Date: Mon, 20 Nov 2000 23:35:34 -0800 From: Julian Elischer <julian@elischer.org> To: Daniel Eischen <eischen@vigrid.com> Cc: Scott Hess <scott@avantgo.com>, jasone@FreeBSD.ORG, arch@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Threads (KSE etc) comments Message-ID: <3A1A25C6.99B1B8F3@elischer.org> References: <Pine.SUN.3.91.1001120124743.17356A-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel Eischen wrote:
>
> With 2 CPUs, you could have 2 KSEs within the KSEG. Nothing changes
> except that the KSEG workload is spread across 2 KSEs running on
> different CPUs. The quantum for the KSEG, regardless of whether
> there are 1 or more KSEs associated with it, remains the same
> (I would advocate a separate quantum in this case, but I think
> I'm outvoted on that front).
not entirely
I think a process using two KSEs in a KSEG should be charged for 2.
>
> This is all for PTHREAD_SCOPE_PROCESS threads. PTHREAD_SCOPE_SYSTEM
> threads will be bound to their own KSEG with one KSE. These will
> act more like LinuxThreads; when one of these threads block in
> the kernel, another one will not be executed (because there are no
> other threads allocated for that KSEG/KSE by the threads library).
well, it WILL do the upcall but the UTS will respond with
"No new thread to schedule, please yield"
>
> --
> Dan Eischen
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-arch" in the body of the message
--
__--_|\ Julian Elischer
/ \ julian@elischer.org
( OZ ) World tour 2000
---> X_.---._/ presently in: Budapest
v
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?3A1A25C6.99B1B8F3>