public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Todd <todd@unm.edu>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	brian jenkins <bjenkins@thresholdnetworks.com>
Subject: Re: What is 2.4 Linux networking performance like compared to BSD?
Date: Thu, 01 Mar 2001 19:03:31 +0300	[thread overview]
Message-ID: <3A9E72D3.36B28B8F@namesys.com> (raw)
In-Reply-To: <Pine.A41.4.33.0102282123180.68876-100000@aix09.unm.edu>

Todd wrote:
> 
> hans,
> 
> we've found that the TCP and UDP performance on 2.4 is *dramatically*
> better than 2.2.  with the acenic gig-e driver on PIII-933 UP (66MHz x
> 64bits PCI) we are getting 993 Mb/s with 2.4.0 with jumbo frames (about
> 850 Mb/s with standard ethernet frames).  the best number we got with 2.2
> was about 650 with jumbos and 550 with standard.
> 
> i'd recommend it's networking performance to anyone.
> 
> todd underwood
> todd@unm.edu
> 
> On Thu, 1 Mar 2001, Hans Reiser wrote:
> 
> > Date: Thu, 01 Mar 2001 02:26:20 +0300
> > From: Hans Reiser <reiser@namesys.com>
> > To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
> > Subject: What is 2.4 Linux networking performance like compared to BSD?
> >
> > I have a client that wants to implement a webcache, but is very leery of
> > implementing it on Linux rather than BSD.
> >
> > They know that iMimic's polymix performance on Linux 2.2.* is half what it is on
> > BSD.  Has the Linux 2.4 networking code caught up to BSD?
> >
> > Can I tell them not to worry about the Linux networking code strangling their
> > webcache product's performance, or not?
> >
> > Hans
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> >

The problem is that I really need BSD vs. Linux experiences, not Linux 2.4 vs.
2.2 experiences, because the webcache industry tends to strongly disparage Linux
networking code, so much better isn't necessarily good enough.

Hans

  reply	other threads:[~2001-03-01 16:36 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 [this message]
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
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=3A9E72D3.36B28B8F@namesys.com \
    --to=reiser@namesys.com \
    --cc=bjenkins@thresholdnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=todd@unm.edu \
    /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