Date: Wed, 4 Nov 1998 09:03:10 -0000 From: James Mansion <james@westongold.com> To: Daniel Eischen <eischen@vigrid.com>, James Mansion <james@westongold.com>, peter@netplex.com.au Cc: current@FreeBSD.ORG, jb@cimlogic.com.au, lists@tar.com Subject: RE: Kernel threading (was Re: Thread Scheduler bug) Message-ID: <32BABEF63EAED111B2C5204C4F4F50201806@WGP01>
next in thread | raw e-mail | index | archive | help
Perhaps I'm being very dense, but you'll have to explain to me what you are concerned about here. *My* concern is that pthread_self, and access to thread-specific data, should be as fast as possible. Writing thread-hot libraries without good thread specific data is irksome to say the least. I'd guess that each 'kernel thread' would benefit from a private page too. James > -----Original Message----- > From: Daniel Eischen [mailto:eischen@vigrid.com] >... > > I'd like to suggest that threads (at least kernel threads) > > should share an address space EXCEPT for a page (or maybe > > more than one) that will have a common address in each thread. > > What about same process threads executing on multiple processors? > > common_address[MAX_CPUS] ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32BABEF63EAED111B2C5204C4F4F50201806>