From: Andrea Arcangeli <andrea@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Linus Torvalds <torvalds@transmeta.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Richard Henderson <rth@redhat.com>
Subject: Re: unregistered changes to the user<->kernel API
Date: Thu, 14 Jun 2001 20:27:44 +0200 [thread overview]
Message-ID: <20010614202744.D2115@athlon.random> (raw)
In-Reply-To: <20010614200328.A2115@athlon.random> <E15AbaZ-00054p-00@the-village.bc.nu>
In-Reply-To: <E15AbaZ-00054p-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Jun 14, 2001 at 07:11:27PM +0100
On Thu, Jun 14, 2001 at 07:11:27PM +0100, Alan Cox wrote:
> 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
I never had doubt that you could do the same in userspace using the
zorocopy functionality (see the old threads with Jeff V. Merkey and
netware when I was saying you don't need it in kernel) so in theory I
totally agree since the first place...
> like the better irq/sendfile stuff why bother merging tux ?
... but in practice x15 is nor open source nor free software and I'd
prefer to have an open choice. I wouldn't even think to merge tux if
zope, apache, thttpd would run as fast as tux of course.
Andrea
next prev parent reply other threads:[~2001-06-14 18:28 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 [this message]
2001-06-14 21:43 ` Albert D. Cahalan
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=20010614202744.D2115@athlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rth@redhat.com \
--cc=torvalds@transmeta.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 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).