From owner-freebsd-hackers  Sun Jan 16 22:42: 0 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from oskar.dev.nanoteq.co.za (oskar.dev.nanoteq.co.za [196.7.114.5])
	by hub.freebsd.org (Postfix) with ESMTP id B9DA4151D7
	for <hackers@FreeBSD.ORG>; Sun, 16 Jan 2000 22:41:53 -0800 (PST)
	(envelope-from rbezuide@oskar.dev.nanoteq.co.za)
Received: (from rbezuide@localhost)
	by oskar.dev.nanoteq.co.za (8.9.3/8.9.0) id IAA21126;
	Mon, 17 Jan 2000 08:40:05 +0200 (SAT)
From: Reinier Bezuidenhout <rbezuide@oskar.dev.nanoteq.co.za>
Message-Id: <200001170640.IAA21126@oskar.dev.nanoteq.co.za>
Subject: Re: Preemptiveness of FreeBSD threads
In-Reply-To: <20000116220322.T302@sturm.canonware.com> from Jason Evans at "Jan 16, 0 10:03:22 pm"
To: jasone@canonware.com (Jason Evans)
Date: Mon, 17 Jan 100 08:40:04 +0200 (SAT)
Cc: archer@lucky.net, hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> My experiments with your test program do exactly what I would expect.  The
> longer the program is run, thu longer the program has to preempt threads,
> which means that given enough time, all threads will run.  If the program
> is run for a short time (less than about 1.5 seconds) then some threads may
> never get to run.

On my system it doesn't matter how long I leave it .. the times it doesn't
work ... e.g. belowe .. it even had enough time to let the varialble wrap ...

jarrow# ./thread
^C
Thread 0x00: 0
Thread 0x01: 0
Thread 0x02: 0
Thread 0x03: 0
Thread 0x04: 0
Thread 0x05: 0
Thread 0x06: 0
Thread 0x07: 0
Thread 0x08: 0
Thread 0x09: 0
Thread 0x0a: -1532959619


So letting it run for longer doesn't help :/


Reinier


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message