archive mirror
 help / color / mirror / Atom feed
From: "Albert D. Cahalan" <>
To: (Alan Cox)
Cc: (Andrea Arcangeli), (Jeff Garzik), (Linus Torvalds), (Ingo Molnar),, (Richard Henderson)
Subject: Re: unregistered changes to the user<->kernel API
Date: Thu, 14 Jun 2001 17:43:52 -0400 (EDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> from "Alan Cox" at Jun 14, 2001 07:11:27 PM

Alan Cox writes:

> I dont see why Tux should be merged. If we have people achieving the same
> performance in user space with the core facilities tux added to the kernel
> like the better irq/sendfile stuff why bother merging tux ?

1. We have khttpd, which should be replaced by something faster.
2. Tux makes a nice example.
3. Tux can be the fastest. If it isn't, it needs more work.

Toward the end of the X15 discussion, Ingo Molnar mentioned
something he'd not implemented yet. I don't recall exactly,
but for sure Tux hasn't run out of optimizations to do.

Also the kernel-CGI feature has not been used in benchmarks.
Tux has been running user code.

IMHO the Tux server could be renamed "khttpd" and dropped in
with whatever is needed to be compatible for existing setups.

      parent reply	other threads:[~2001-06-14 21:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-14 17:12 unregistered changes to the user<->kernel API Andrea Arcangeli
2001-06-14 17:16 ` Andrea Arcangeli
2001-06-14 17:21   ` Andrea Arcangeli
2001-06-14 17:32     ` Richard Henderson
2001-06-14 17:47       ` Andrea Arcangeli
2001-06-14 18:16         ` Andrea Arcangeli
2001-06-14 18:17         ` Richard Henderson
2001-06-14 18:10       ` Alexander Viro
2001-06-14 17:25 ` Jeff Garzik
2001-06-14 17:44   ` Andrea Arcangeli
2001-06-14 17:52     ` Jeff Garzik
2001-06-14 18:03       ` Andrea Arcangeli
2001-06-14 18:11         ` Alan Cox
2001-06-14 18:27           ` Andrea Arcangeli
2001-06-14 21:43           ` Albert D. Cahalan [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).