From: Matt Kavanagh <matthew@teh.ath.cx>
To: Ram Chandar <rcknl@qz.port5.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux Routing Performance inferior?
Date: Wed, 8 Sep 2004 20:01:57 +0100 [thread overview]
Message-ID: <20040908190157.GA2109@teh.ath.cx> (raw)
In-Reply-To: <200409071000.58455.rchandar-knl@qz.port5.com>
On Wed, Sep 08, 2004 at 11:06:17PM +0530, Ram Chandar wrote:
>
> Quoted from a recent mail to freebsd mailing list.
>
> "FreeBSD (5.x) can route 1Mpps on a 2.8G Xeon while
> Linux can't do much more than 100kpps"
>
> http://lists.freebsd.org/pipermail/freebsd-net/2004-September/004840.html
>
> Is this indeed the case?
Seems to be pretty much just biased conjecture IMO. I wouldn't
dismiss the possibility of FreeBSD having (in some situations)
significantly better routing performance than linux in the same
situation..but getting me to believe that would require proper,
objective benchmarks.
All from a user's perspective.
prev parent reply other threads:[~2004-09-08 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 17:36 Linux Routing Performance inferior? Ram Chandar
2004-09-08 17:58 ` William Stearns
2004-09-08 18:41 ` Nathan Bryant
2004-09-08 19:21 ` Tomasz Torcz
2004-09-08 18:56 ` Norbert van Nobelen
2004-09-08 19:01 ` Matt Kavanagh [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:
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=20040908190157.GA2109@teh.ath.cx \
--to=matthew@teh.ath.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=rcknl@qz.port5.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.