Re: kqueue giant-locking (&kq_Giant, locking)
From: Garrett Wollman (wollman_at_khavrinen.lcs.mit.edu)
Date: 04/17/04
- Previous message: Brian F. Feldman: "Re: kqueue giant-locking (&kq_Giant, locking)"
- In reply to: Brian F. Feldman: "Re: kqueue giant-locking (&kq_Giant, locking)"
- Next in thread: Brian F. Feldman: "Re: kqueue giant-locking (&kq_Giant, locking)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 17 Apr 2004 00:47:06 -0400 (EDT) To: green@freebsd.org
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
_______________________________________________
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"
- Previous message: Brian F. Feldman: "Re: kqueue giant-locking (&kq_Giant, locking)"
- In reply to: Brian F. Feldman: "Re: kqueue giant-locking (&kq_Giant, locking)"
- Next in thread: Brian F. Feldman: "Re: kqueue giant-locking (&kq_Giant, locking)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]