Date: Sat, 20 Nov 1999 22:27:27 -0700 From: Nate Williams <nate@mt.sri.com> To: Julian Elischer <julian@whistle.com> Cc: Nate Williams <nate@mt.sri.com>, "Daniel M. Eischen" <eischen@vigrid.com>, freebsd-arch@freebsd.org Subject: Re: Threads Message-ID: <199911210527.WAA13788@mt.sri.com> In-Reply-To: <Pine.BSF.4.10.9911202123310.6767-100000@current1.whistle.com> References: <199911210514.WAA13707@mt.sri.com> <Pine.BSF.4.10.9911202123310.6767-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > New calls must be able to return and say > > > "hey it's not me returnuing, but actually a new KSE, " > > > > Not only that, but you need a way for it to be 'aborted' out and have it > > cleanup as it goes. I suspect that this will require re-writing a large > > number of syscalls with threading in mind, and leaving the 'old' calls > > in place will allow more flexibility as things change. > > > > I could envision the 'old' calls going away at some point as the new > > calls get completely fleshed out and tested, to be replaced with simple > > wrappers for the threaded calls. > > Maybe in the libraries, but we will need to keep the old syscalls in the > kernel effectively forever. (for old binaries) It's not much of a cost.. > (look at linux emulation). Like I said above, the old calls could be simple wrappers for the new 'threaded' syscalls, which gives us the ability to have both. The 'old' implementations would go away, not the old calls. Nate 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?199911210527.WAA13788>