Date: Wed, 21 Nov 2001 18:45:08 -0600 From: Alfred Perlstein <bright@mu.org> To: Julian Elischer <julian@elischer.org> Cc: arch@freebsd.org Subject: Re: Kernel Thread scheduler Message-ID: <20011121184508.T13393@elvis.mu.org> In-Reply-To: <Pine.BSF.4.21.0111211208410.35591-100000@InterJet.elischer.org>; from julian@elischer.org on Wed, Nov 21, 2001 at 04:39:18PM -0800 References: <Pine.BSF.4.21.0111211208410.35591-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Julian Elischer <julian@elischer.org> [011121 18:40] wrote: > > > Peter, John (Baldwin) and I got to gether yesterday and thrashed > out the mechanisms behind the KSE/thread scheduler. > This allows us to go ahead and start coding again, now that we know what > we are aiming at. > > Here is the basic mechanism. [snip] Since my request is about one one thousandth as complex as this I'm just going to ask: Will this stuff be usable as a lightweight mechanism inside the kernel? Case in point, could nfsd be changed to only have one process (instead of many) while still being able to block and get an upcall? -Alfred 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?20011121184508.T13393>