From owner-freebsd-arch Thu Dec 9 21: 4:28 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 6F33C14CBF for ; Thu, 9 Dec 1999 21:04:24 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id GAA14415 for ; Fri, 10 Dec 1999 06:04:22 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id GAA33652 for freebsd-arch@freebsd.org; Fri, 10 Dec 1999 06:04:21 +0100 (MET) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 9342714E24 for ; Thu, 9 Dec 1999 21:04:13 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40337>; Fri, 10 Dec 1999 15:56:00 +1100 Content-return: prohibited Date: Fri, 10 Dec 1999 16:02:40 +1100 From: Peter Jeremy Subject: Re: Thread scheduling In-reply-to: ; from chuckr@picnic.mat.net on Fri, Dec 10, 1999 at 03:40:40PM +1100 To: Chuck Robey Cc: freebsd-arch@freebsd.org Message-Id: <99Dec10.155600est.40337@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-10 15:40:40 +1100, Chuck Robey wrote: >That is, is it important at all that all processors be doing the same >multithreading task (if it's multithreaded, and wants it) at exactly the >same time? I don't think this is guaranteed anywhere. In any case, IMHO it would be virtually impossible for a system to provide such a guarantee - consider a system which provided such a guarantee and currently has two threads executing on two CPUs. An interrupt then occurs on one CPU - what happens to the thread on the other CPU (which hasn't seen the interrupt)? What happens if (as a result of the interrupt) a higher priority process becomes runnable? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message