Date: Fri, 16 Apr 2004 23:30:47 -0400 From: "Brian F. Feldman" <green@freebsd.org> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: arch@freebsd.org Subject: Re: kqueue giant-locking (&kq_Giant, locking) Message-ID: <200404170330.i3H3Ul0t032543@green.homeunix.org> In-Reply-To: Message from Garrett Wollman <wollman@khavrinen.lcs.mit.edu> <200404170253.i3H2rmAV021500@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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. \,,,,,,,,,,,,,,,,,,,,,,\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200404170330.i3H3Ul0t032543>