From owner-freebsd-arch Sun Nov 28 16:18:56 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 8458714BC3 for ; Sun, 28 Nov 1999 16:18:53 -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 BAA29832 for ; Mon, 29 Nov 1999 01:18:53 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id BAA60427 for freebsd-arch@freebsd.org; Mon, 29 Nov 1999 01:18:53 +0100 (MET) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 6478414BC3 for ; Sun, 28 Nov 1999 16:18:42 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40352>; Mon, 29 Nov 1999 11:11:17 +1100 Content-return: prohibited Date: Mon, 29 Nov 1999 11:15:41 +1100 From: Peter Jeremy Subject: Re: Threads stuff In-reply-to: <38417A7F.B23C701D@vigrid.com> To: freebsd-arch@freebsd.org Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov29.111117est.40352@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <3840B1EC.4614AAF0@vigrid.com> <199911281721.JAA45015@apollo.backplane.com> <38417A7F.B23C701D@vigrid.com> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-29 05:54:55 +1100, Daniel M. Eischen wrote: >Do we really want to be able to bind a _thread_ to a CPU? Yes. > Wouldn't it be sufficient to be able to bind a process to a CPU? Not really. If a process has multiple threads, it makes sense to be able to specify CPU affinity for each thread, since each thread can be scheduled independently. If you've got a multi-threaded process, I'm not sure why you'd want to bind it as a whole to a single CPU. This implies that only one thread can ever execute at once - which removes one major use for threads. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message