On Fri, 6 Jun 2003 itojun@iijlab.net wrote:

> 	what i do care in IRS implementation is net_data portion.  it manages
> 	data that are needed to be thread-specific, and manages name lookup
> 	function dispatches.  nsdispatch/nsswitch does not have anything
> 	about the former portion.  as we start providing thread-safe library
> 	implementations, we will need to re-do what ISC did with net_data.

Ok, what data are we talking about? I'm gathering that net_data keeps data
for gethostent() and gethostent_r(). Why?

I've always seen gethostent() as being documented as being _NOT_ thread
safe. Why go to the trouble of making thread-safe calls that no one
expects to be thread safe? Anyone who uses them will have taken thread
safety protections already. ??

Also, I thought that gethostent_r() just used passed-in storage. Why make
it thread safe, when it's explicitly encapsulated?

I greatly appreciate everyone's efforts to make NetBSD as thread-safe as
possible, but shouldn't we be consistent with what other OSs are doing?
I'd consider Solaris a good model to follow since they've been doing
threads for so long. :-)

Take care,

Bill