Re: kqueue giant-locking (&kq_Giant, locking)

From: Brian F. Feldman (green_at_freebsd.org)
Date: 04/17/04

  • Next message: Garrett Wollman: "Re: kqueue giant-locking (&kq_Giant, locking)" 
    To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Date: Fri, 16 Apr 2004 23:30:47 -0400

    Garrett Wollman <wollman@khavrinen.lcs.mit.edu> wrote:
    > In article <200404170212.i3H2Cg8n031749@green.homeunix.org> you write:
    > >1. The recursion has been removed from kqueue. This means kqueues cannot be
    > > added to other kqueues for EVFILT_READ -- yes, that ability has been
    > > around since r1.1 of kern_event.c,
    >
    > Actually, I'm fairly certain that Jonathan considered this to be a
    > fairly important property of kqueue and his papers do mention it.
    > It was done that way specifically to allow a kqueue to be included in
    > some larger application's event polling loop without needing to know
    > how it was implemented.

    I can't imagine a well-designed applications has kqueues of kqueues. I
    didn't remove the file descriptor polling interface, I removed the file
    descriptor kqueue interface. 

    -- 
Brian Fundakowski Feldman                           \'[ FreeBSD ]''''''''''\
  <> green@FreeBSD.org                               \  The Power to Serve! \
 Opinions expressed are my own.                       \,,,,,,,,,,,,,,,,,,,,,,\
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
  • Next message: Garrett Wollman: "Re: kqueue giant-locking (&kq_Giant, locking)"