Date: Sun, 31 Oct 1999 22:15:01 -0500 (EST) From: Daniel Eischen <eischen@vigrid.com> To: eischen@vigrid.com, julian@whistle.com Cc: freebsd-arch@freebsd.org Subject: Re: Threads models and FreeBSD. Message-ID: <199911010315.WAA16785@pcnet1.pcnet.com>
next in thread | raw e-mail | index | archive | help
Julian Elischer wrote: > On Sun, 31 Oct 1999, Daniel Eischen wrote: [...] > > 10.) Quick access to curthread and thread specific data. We shouldn't > > have to enter the kernel to get this. This should also be true > > for threads spread across multiple [lightweight] processes. > > > fair enough.. (though very much a 'request' than a major design goal) Well, you could argue that a design that forced a system call whenever the current thread or TSD was needed was a bad design. I would imagine every pthread function needs to get at the current thread, so that would force at least one system call for each pthread call. > > 12.) A libpthread that can be linked with libc. > > At this stage, an implementation detail, can I leave this till a later > stage? OK 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?199911010315.WAA16785>