Date: Sun, 28 Nov 1999 20:07:37 -0500 From: "Daniel M. Eischen" <eischen@vigrid.com> To: Julian Elischer <julian@whistle.com> Cc: peter.jeremy@alcatel.com.au, freebsd-arch@freebsd.org Subject: Re: Threads stuff Message-ID: <3841D1D9.A048355D@vigrid.com> References: <Pine.BSF.4.10.9911281626180.544-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote: > > I think there is confusion here.. > > The way Dan and I have been discussing it (you need to go back and read > the old mail) the process creates several thread classes. Thread classes > can be bound to a CPU and can have different system priorities. They are > implemted in FreeBSD by rfork()ing a new process (called a subprocess. > The scheduler then assigns threads to the subprocess. Effectively > assigning them to a class. > if the class is "all threads herein run on CPU1" tehn you get what you > want.. > Dan left of the "sub". Right, so if you wanted to bind a _single_ thread to a CPU, you bind your chosen thread to a subprocess, and the subprocess to the CPU. I did leave out sub. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3841D1D9.A048355D>