Skip to contentSkip to conversation

Adding kernel-level identd dispatcher

PATCH In review Edward Chernenko 3 participants 10 messages Mar 24, 2006 – Mar 28, 2006

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Adding kernel-level identd dispatcher

This patch adds ident daemon to net/gnuidentd/
directory.
Apply to: 2.6.15.1.
Patch is here:
http://unwd.sourceforge.net/gnuidentd-2.6.15.patch

I used two threads: one for connections handling and another for tracking /etc/passwd changes through inotify.
Additionally, root can set users hiding rules using file in /proc.

I'm awaiting your notes/tips.
Please CC me to <[email protected]>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

#1 lore raw
Quoted 6 lines

This patch adds ident daemon to net/gnuidentd/
directory.
Apply to: 2.6.15.1.
Patch is here:
http://unwd.sourceforge.net/gnuidentd-2.6.15.patch

Quoted 7 lines

I used two threads: one for connections handling and another for tracking /etc/passwd changes through inotify.
Additionally, root can set users hiding rules using file in /proc.

I'm awaiting your notes/tips.

I dislike this concept. khttpd once tried the same (moving userspace to kernelspace) -- and it's out again.

Jan Engelhardt

#2 lore raw
Quoted 6 lines
Quoted 6 lines

This patch adds ident daemon to net/gnuidentd/
directory.
Apply to: 2.6.15.1.
Patch is here:
http://unwd.sourceforge.net/gnuidentd-2.6.15.patch

Quoted 7 lines
Quoted 7 lines

I used two threads: one for connections handling and another for tracking /etc/passwd changes through inotify.
Additionally, root can set users hiding rules using file in /proc.

I'm awaiting your notes/tips.

Are you even allowed to use the name "GNU identd"?
I'm not seeing your identd listed on GNU.org, that is, having a page at http://www.gnu.org/software/identd/ like e.g. GRUB does.

Jan Engelhardt

#3 lore raw
Quoted 7 lines · --- Jan Engelhardt

Are you even allowed to use the name "GNU identd"? I'm not seeing your identd listed on GNU.org, that is, having
a page at http://www.gnu.org/software/identd/ like e.g. GRUB does.

Only portable (but not Linux-specific) software coud be placed in gnu.org, if you don't know.

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

#4 lore raw
In reply to Edward Chernenko
Quoted 12 lines · Edward Chernenko

This patch adds ident daemon to net/gnuidentd/
directory.
Apply to: 2.6.15.1.
Patch is here:
http://unwd.sourceforge.net/gnuidentd-2.6.15.patch

I used two threads: one for connections handling and another for tracking /etc/passwd changes through inotify.
Additionally, root can set users hiding rules using file in /proc.

Quoted 4 lines

I'm awaiting your notes/tips.
Please CC me to <[email protected]>

Justification, please.

You haven't even tried to explain to us what is so broken about the userland identd that it needs to be replaced with a kernel version.

Cheers,
Trond

#5 lore raw

--- Trond Myklebust <[email protected]>

Quoted 8 lines · wrote:

Justification, please.

You haven't even tried to explain to us what is so broken about the
userland identd that it needs to be replaced with a kernel version.

My point is that everything which follows this
conditions should be moved into kernel:
- must dispatch requests in a fixed time
- must work rarely, sleep most time
- must depend on internal kernel variables (for
example, established connections table)

Don't forget that many years ago there was echo daemon in userspace. But as it's highly effective to dispatch all echo requests in kernel, it was moved into low-level TCP implementation.

I think that ident protocol also matches this
criteria.

Edward Chernenko <[email protected]>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

#6 lore raw
Quoted 18 lines · Edward Chernenko

--- Trond Myklebust <[email protected]>

Quoted 8 lines · wrote:

Justification, please.

You haven't even tried to explain to us what is so broken about the
userland identd that it needs to be replaced with a kernel version.

My point is that everything which follows this
conditions should be moved into kernel:
- must dispatch requests in a fixed time
- must work rarely, sleep most time
- must depend on internal kernel variables (for
example, established connections table)

Quoted 7 lines

Don't forget that many years ago there was echo daemon in userspace. But as it's highly effective to dispatch all echo requests in kernel, it was moved into low-level TCP implementation.

I think that ident protocol also matches this
criteria.

Most servers are designed for low latency. A lot of them sleep a lot, and a fair number of them also go poking around the kernel variables in /proc (which exists precisely in order to export internal kernel variables to userspace programs). I'll bet even your average Oracle database application fits those criteria.

Echo made sense to move into the kernel because in addition to the above it is a required feature on all Internet hosts, is pretty much stateless (and/or depends only on internal IP stack state), and needs extra low latency because it is designed to be used for timing purposes by clients.
The same criteria hardly apply to identd.

Cheers,
Trond

#7 lore raw

--- Trond Myklebust <[email protected]>

Quoted 10 lines · wrote:

Most servers are designed for low latency. A lot of them sleep a lot,
and a fair number of them also go poking around the kernel variables
in /proc (which exists precisely in order to export internal kernel
variables to userspace programs). I'll bet even your average Oracle
database application fits those criteria.

Quoted 10 lines

Echo made sense to move into the kernel because in addition to the above
it is a required feature on all Internet hosts, is pretty much stateless
(and/or depends only on internal IP stack state), and needs extra low
latency because it is designed to be used for timing purposes by
clients.
The same criteria hardly apply to identd.

If so, then why khttpd _was_ included into kernel?

Edward Chernenko <[email protected]>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

#8 lore raw
Quoted 25 lines · Edward Chernenko

--- Trond Myklebust <[email protected]>

Quoted 10 lines · wrote:

Most servers are designed for low latency. A lot of them sleep a lot,
and a fair number of them also go poking around the kernel variables
in /proc (which exists precisely in order to export internal kernel
variables to userspace programs). I'll bet even your average Oracle
database application fits those criteria.

Quoted 10 lines

Echo made sense to move into the kernel because in addition to the above
it is a required feature on all Internet hosts, is pretty much stateless
(and/or depends only on internal IP stack state), and needs extra low
latency because it is designed to be used for timing purposes by
clients.
The same criteria hardly apply to identd.

Quoted 1 line

If so, then why khttpd _was_ included into kernel?

That has been widely acknowledged as a mistake. You'll note that khttpd was removed prior to the release of linux-2.6.0. Nobody misses it.

Cheers,
Trond

#9 lore raw

--- Trond Myklebust <[email protected]>

Quoted 8 lines · wrote:
Quoted 2 lines

If so, then why khttpd _was_ included into kernel?

That has been widely acknowledged as a mistake.
You'll note that khttpd
was removed prior to the release of linux-2.6.0.
Nobody misses it.

That's bad. I think that some people need this, so my module will be distributed like Tux webserver, separately from kernel.

Anyway, can you help me by explaining your opinion about my code, not about development phylosophy? That's my first work and it's important to me to find if I done something unefficient.

Edward Chernenko <[email protected]>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com