From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Edward Chernenko <edwardspec@yahoo.com>
Cc: linux-kernel@vger.kernel.org, edwardspec@gmail.com
Subject: Re: [PATCH 2.6.15] Adding kernel-level identd dispatcher
Date: Tue, 28 Mar 2006 10:53:27 -0500 [thread overview]
Message-ID: <1143561207.8009.58.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20060328154841.74612.qmail@web37708.mail.mud.yahoo.com>
On Tue, 2006-03-28 at 07:48 -0800, Edward Chernenko wrote:
>
> --- Trond Myklebust <trond.myklebust@fys.uio.no>
> 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.
> >
> > 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?
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
next prev parent reply other threads:[~2006-03-28 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 16:21 Edward Chernenko
2006-03-25 19:18 ` Jan Engelhardt
2006-03-26 23:12 ` Jan Engelhardt
2006-03-27 12:27 ` Edward Chernenko
2006-03-27 17:56 ` Trond Myklebust
2006-03-28 10:14 ` Edward Chernenko
2006-03-28 13:36 ` Trond Myklebust
2006-03-28 15:48 ` Edward Chernenko
2006-03-28 15:53 ` Trond Myklebust [this message]
2006-03-28 20:30 ` Edward Chernenko
2006-03-26 19:49 Edward Chernenko
2006-03-26 22:42 ` Ray Lee
2006-03-28 1:59 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1143561207.8009.58.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=edwardspec@gmail.com \
--cc=edwardspec@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®