Andi Kleen wrote:
On Wednesday 01 February 2006 21:26, Jeff Garzik wrote:
Andi Kleen wrote:
But I don't think Van's design is supposed to be exposed to user space.
It is supposed to be exposed to userspace AFAICS.
Then it's likely insecure and root only, unless he knows some magic
that we don't.
Once packets classified to be delivered to a specific local host socket,
what further operations are require privs? What received packet data
cannot be exposed to userspace?
I hope it's not just PF_PACKET mmap rings with a user space TCP library.
Why?
It's still in the kernel, just in process context.
Incorrect. Its in the userspace app (though usually via a library).
See slides 26 and 27.
I mean the Linux implementation is in the kernel, but in user context.
Yes, I know what you meant. My answer still stands... Certainly older
applications that use only read(2) and write(2) must continue to work.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
