Date: Sat, 17 Apr 2004 00:47:06 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: green@freebsd.org Cc: arch@freebsd.org Subject: Re: kqueue giant-locking (&kq_Giant, locking) Message-ID: <200404170447.i3H4l6Hn021993@khavrinen.lcs.mit.edu> In-Reply-To: <200404170330.i3H3Ul0t032543@green.homeunix.org> References: <wollman@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <200404170330.i3H3Ul0t032543@green.homeunix.org> you write: >I can't imagine a well-designed applications has kqueues of kqueues. I can in about five seconds' worth of thought. Suppose you have library X. It accomplishes some task asynchronously (it doesn't matter what or how), and provides a descriptor that the calling application must poll for completion. Now use that library into an application that has its own event loop. This is one of the specific motivating examples behind doing kqueue rather than simply extending poll() or select(). Please go and read the papers before you continue down this path. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200404170447.i3H4l6Hn021993>