All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cort Dougan <cort@fsmlabs.com>
To: Diego Calleja <DiegoCG@teleline.es>
Cc: John Stoffel <stoffel@casc.com>, Dan Kegel <dank@kegel.com>,
	"David S. Miller" <davem@redhat.com>,
	khttpd-users@alt.org, linux-kernel@vger.kernel.org
Subject: Re: Tux in main kernel tree? (was khttpd rotten?)
Date: Mon, 6 May 2002 13:18:04 -0600	[thread overview]
Message-ID: <20020506131804.G13077@host110.fsmlabs.com> (raw)
In-Reply-To: <3CD5ECEE.E6C0B894@kegel.com> <Pine.LNX.4.44.0205061608300.26867-100000@mustard.heime.net> <15574.52864.321544.44124@gargle.gargle.HOWL> <20020506210727.4ed05ba1.DiegoCG@teleline.es>

I put MPI in the kernel and got a huge performance advantage from it.  I
think that was a valuable idea and the results show that's definitely the
case.  I don't think the argument could ever be made that it belongs in the
main kernel, though.  A separate project with a loadable module is
definitely the way to go for these things.

"Keep that out of my kernel" is an old operating system design adage that
isn't paid attention to enough.

} > An httpd server is a *user space* issue, not a kernel issue.
} 
} It's true. But I'd be an idiot if I can improve performance and I don't do it.
} 
} However, if an httpd can be as fast as an kernel space httpd it'd be a bad thing to put it
} in kernel space.

  reply	other threads:[~2002-05-06 19:20 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 [this message]
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
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=20020506131804.G13077@host110.fsmlabs.com \
    --to=cort@fsmlabs.com \
    --cc=DiegoCG@teleline.es \
    --cc=dank@kegel.com \
    --cc=davem@redhat.com \
    --cc=khttpd-users@alt.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stoffel@casc.com \
    /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.