On 5/5/07, Davide Libenzi <[email protected]> wrote:
But we have our own *sane* version of WaitForMultipleObjects, and it's
called poll(2).
No, we don't. Don't start all over again. The interface of poll it
to primitive. See the kevent code, each record is, IIRC, 16 bytes in
size to return more data. For poll you only have bits.
Now, considering that POSIX is the backbone of Linux (and *nix in
general), and considering that we certainly cannot drop existing POSIX
semantics, where the lagacy code will come from?
The legacy part comes from all this extra "make into a file
descriptor" stuff which is new, not needed now and especially not when
a full solution is available.
I really do not understand your point. You're too smart to not appreciate
the beauty and the simmetry of objects that responds to a common interface
(our files, win32 handles), and that fits our existing kernel infrastructure.
You're blinded by this symmetry. Not everything that looks like a
good fit is a good idea. This is one case. Get over it, poll is not
powerful enough to serve as the unifying event mechanism.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
