From: "David L. Parsley" <parsley@linuxjedi.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Hans Reiser <reiser@namesys.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
mingo@redhat.com
Subject: Re: What is 2.4 Linux networking performance like compared to BSD?
Date: Thu, 01 Mar 2001 23:57:05 -0500 [thread overview]
Message-ID: <3A9F2821.A9B20002@linuxjedi.org> (raw)
In-Reply-To: <E14YYcH-0008NK-00@the-village.bc.nu>
<snip stuff about someone using linux for a web cache>
Alan Cox wrote:
> The extreme answer to the 2.4 networking performance is the tux specweb
> benchmarks but they dont answer for all cases clearly.
However, I think you've hit the nail on the head here; much of tux is
just general-purpose network file-blasting. The right hacker could turn
it into the fastest web-cache on the planet with the right modules. I
believe Ingo already did a basic ftp server based on tux, just to
demonstrate this generality.
Ingo? Am I crazy or enlightened?
regards,
David
next prev parent reply other threads:[~2001-03-02 4:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 23:26 What is 2.4 Linux networking performance like compared to BSD? Hans Reiser
2001-03-01 4:25 ` Todd
2001-03-01 16:03 ` Hans Reiser
2001-03-01 17:04 ` Nathan Dabney
2001-03-01 18:36 ` Hans Reiser
2001-03-01 19:16 ` David Weinehall
2001-03-01 19:19 ` Alan Cox
2001-03-02 4:57 ` David L. Parsley [this message]
2001-03-01 19:22 ` Nathan Dabney
2001-03-02 9:02 ` Henning P. Schmiedehausen
2001-03-02 13:00 ` Gregory Maxwell
2001-03-05 8:09 ` Re[2]: " linuxjob
2001-03-02 14:28 ` Alan Cox
2001-03-01 17:17 ` God
2001-03-01 18:04 ` Lincoln Dale
2001-03-01 10:32 ` Alan Cox
2001-03-01 17:15 ` James Lewis Nance
2001-03-01 18:38 ` Hans Reiser
2001-03-01 19:25 ` Tigran Aivazian
2001-03-01 23:30 ` Hans Reiser
2001-03-01 20:26 ` kuznet
2001-03-02 3:05 ` linuxjob
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=3A9F2821.A9B20002@linuxjedi.org \
--to=parsley@linuxjedi.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reiser@namesys.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