Date: Wed, 7 Mar 2001 09:33:06 +0800 From: David Xu <bsddiy@21cn.com> To: Nate Williams <nate@yogotech.com> Cc: Daniel Eischen <eischen@vigrid.com>, java@FreeBSD.ORG Subject: Re[2]: Java and libc/libpthread Message-ID: <732348376.20010307093306@viasoft.com.cn> In-Reply-To: <15013.11891.57267.160163@nomad.yogotech.com> References: <15013.10075.22410.630598@nomad.yogotech.com> <Pine.SUN.3.91.1010306131003.21096A-100000@pcnet1.pcnet.com> <15013.11891.57267.160163@nomad.yogotech.com>
index | next in thread | previous in thread | raw e-mail
Hello Nate,
Wednesday, March 07, 2001, 2:37:39 AM, you wrote:
>> > > I'm currently working on an NxN libpthread implementation as
>> > > an interim solution until we get KSEs. The goal is to get
>> > > this done before 5.0.
>> >
>> > How is this different from the current implementation?
>>
>> File descriptors will not be made non-blocking like they are
>> currently in libc_r. When a thread blocks on I/O, it _really_
>> blocks -- no other threads will be scheduled within that
>> [rfork_thread'd/cloned] process.
NW> So, reversing the logic ('not be made non-blocking'), file descriptors
NW> will be made blocking? This doesn't seem like progress, but I may not
NW> understand the implications.
>> Other PTHREAD_SCOPE_SYSTEM
>> [rfork_thread] threads will continue to run.
NW> So, you're going to create a system similar to Linux-threads, but with a
NW> more BSD-like license?
NW> Nate
hope KSE will be implemented as soon as possible, it will let multiple
blocking I/O run in one process at same time. I see this is a great
progress. it seems libpthread will become simpler and smaller and
more efficient than old libc_r.
--
Best regards,
David Xu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-java" in the body of the message
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?732348376.20010307093306>