From: Martin Dalecki <dalecki@evision-ventures.com>
To: "David S. Miller" <davem@redhat.com>
Cc: akpm@zip.com.au, indigoid@higherplane.net, dank@kegel.com,
khttpd-users@alt.org, linux-kernel@vger.kernel.org
Subject: Re: khttpd rotten?
Date: Thu, 09 May 2002 21:39:57 +0200 [thread overview]
Message-ID: <3CDAD08D.2090102@evision-ventures.com> (raw)
In-Reply-To: <20020509114009.GD3855@higherplane.net> <20020509.042938.78984470.davem@redhat.com> <3CDACE73.6692A31E@zip.com.au> <20020509.123540.85382726.davem@redhat.com>
Uz.ytkownik David S. Miller napisa?:
> From: Andrew Morton <akpm@zip.com.au>
> Date: Thu, 09 May 2002 12:30:59 -0700
>
> The concern with moving one (major) application into the
> kernel is that this will weaken the testing/motivation to get
> zerocopy, aio and sophisticated notifications working well
> for userspace.
>
> Actually, to the contrary, TUX was in fact an impetus for the
> userlevel zerocopy and AIO bits :-)
>
> I personally don't see anything wrong with something like the
> TUX engine being in there. At the same time I want to reiterate what
> Ingo said which is what we can do in userspace catches up to what
> TUX can do then we pull it out and move on to the next thing :-)
It's far easiet to add then to remove. Trust me ;-).
I vote against both of them: tux and khttpd are should have
no place in the kernel of a General Pupose OS kernel.
next prev parent reply other threads:[~2002-05-09 20:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 0:28 khttpd rotten? Dan Kegel
2002-05-06 2:14 ` David S. Miller
2002-05-06 2:39 ` Dan Kegel
2002-05-06 10:23 ` Christoph Hellwig
2002-05-06 11:28 ` [PATCH] " Dan Kegel
2002-05-06 17:23 ` Luigi Genoni
2002-05-09 9:49 ` David S. Miller
2002-05-09 10:09 ` Christoph Hellwig
2002-05-09 13:04 ` Luigi Genoni
2002-05-11 0:13 ` Ken Brownfield
2002-05-06 14:17 ` Tux in main kernel tree? (was khttpd rotten?) Roy Sigurd Karlsbakk
2002-05-06 16:08 ` Andy Carlson
2002-05-06 23:35 ` Anton Blanchard
2002-05-07 14:42 ` Alan Cox
2002-05-07 15:03 ` Andrea Arcangeli
2002-05-07 15:26 ` Alan Cox
2002-05-07 15:38 ` Andrea Arcangeli
2002-05-07 16:02 ` Luigi Genoni
2002-05-06 17:21 ` Dan Kegel
2002-05-06 18:42 ` John Stoffel
2002-05-06 19:07 ` Diego Calleja
2002-05-06 19:18 ` Cort Dougan
2002-05-06 20:47 ` Michael Rothwell
2002-05-09 11:20 ` Appications in kernelspace (was:Tux in main kernel tree?) Anders Peter Fugmann
2002-05-06 21:52 ` Tux in main kernel tree? (was khttpd rotten?) Paul Jakma
2002-05-09 11:28 ` john slee
2002-05-07 3:00 ` J Sloan
2002-05-09 11:40 ` khttpd rotten? john slee
2002-05-09 11:29 ` David S. Miller
2002-05-09 19:30 ` Andrew Morton
2002-05-09 19:35 ` David S. Miller
2002-05-09 19:39 ` Martin Dalecki [this message]
2002-05-10 10:20 ` Andi Kleen
2002-05-10 10:49 ` David S. Miller
2002-05-09 20:12 ` Ian Molton
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=3CDAD08D.2090102@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=akpm@zip.com.au \
--cc=dank@kegel.com \
--cc=davem@redhat.com \
--cc=indigoid@higherplane.net \
--cc=khttpd-users@alt.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.