On Fri, Mar 16, 2001 at 12:59:24PM +0800, David Xu wrote:
> Hello Julian,
> Friday, March 16, 2001, 12:18:15 PM, you wrote:
> JE> David Xu wrote:
> >> 
> >>    I wonder status of KSE, I am dreaming rewrite our application
> >> server using kqueue+pthread(KSE), current, we use poll()+pthread
> >> because pthread does not work with kqueue at present.
> >> 
> >> --
> >> Best regards,
> >> David Xu
> JE> KSE is not into coding yet.
> JE> we have a basic design and have soem documents but
> JE> have been waiting for the SMPng stuff to settle a bit before we
> JE> hit the kernel with a second huge change.
> JE> It will not be ready for a long time. do not assume that it
> JE> will be ready for when you need it becasue it will not.
> I know KSE is not related to SMP and will run on UP. my primary
> idea is want to run parellel I/O task in same process with pthread,
> simply because FreeBSD pthread does not allow me to do multipile
> I/O tasks at same time on disk file, of course, it is also conflicted
> with SYSV IPC, so I think of KSE. I don't care about SMP, CPU is
> enough fast now, I have already seen 1.3G hz CPU, how fast! I think
> Intel and AMD can very easy to double their CPU clock, hope I can see
> 3Ghz CPU in next year. I really do think KSE should work before SMP,
> but it is obvious not. think about Apache 2.0, it is already
> multi-threaded, FreeBSD pthread will be blocked at disk I/O, it is very
> bad for Apache 2.0 .

I believe Julian's SMP-related comments were referring to the fact that
SMP development has rendered the -current kernel somewhat unstable at
times (to say the least).  KSE-related work would introduce yet another
probable path for instabilities, and the developers prefer dealing with
one huge monster at a time.  There is also the fact that KSE work shall
most probably touch many places in the kernel that SMP development also
touches - yet another reason to postpone KSE until SMP is kind-of done.


You have, of course, just begun reading the sentence that you have just finished 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to