Adding kernel-level identd dispatcher
2006/3/25, Jan Engelhardt <[email protected]>:
Quoted 2 lines
I dislike this concept. khttpd once tried the same
(moving
Quoted 2 lines
userspace to kernelspace) -- and it's out again.
Comparing with khttpd, we have no need to make transfers between
userspace and kernelspace; additionally, ident daemon depends on
kernel connections table. This is very efficient to avoid using proc
interface by userspace program here.
--
Edward Chernenko <[email protected]>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Quoted 2 lines
Comparing with khttpd, we have no need to make
transfers between userspace and kernelspace;
For any of this to be motivating to anyone here, you'll have to present an argument as to why this can't be done in userspace. identd isn't a terribly complex thing -- one would think that a carefully crafted userspace daemon could saturate any reasonable network connection.
Conversely, if it can't be done fast from userspace, then people to hear about that. That means that there's some task the kernel needs to be made more faster at doing.
And if whatever potential performance problems with the kernel are fixed, then all applications, including your userspace identd too, will benefit from the fixes.
Quoted 8 lines · Edward Chernenko
Comparing with khttpd, we have no need to make transfers between
userspace and kernelspace; additionally, ident daemon depends on
kernel connections table. This is very efficient to avoid using proc
interface by userspace program here.
Check out the pidentd in Debian. It uses netlink instead of procfs which is much more scalable.
Cheers,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt