From: Nathan Bryant <nbryant@optonline.net>
To: William Stearns <wstearns@pobox.com>
Cc: Ram Chandar <rcknl@qz.port5.com>,
ML-linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux Routing Performance inferior?
Date: Wed, 08 Sep 2004 14:41:34 -0400 [thread overview]
Message-ID: <413F525E.3010408@optonline.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0409081354470.2985@sparrow>
William Stearns wrote:
> Good afternoon, Ram,
>
> On Wed, 8 Sep 2004, 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?
>
>
> I'm sure others here have far better examples, but one post to the
> netfilter-devel list last December provided an example of a firewall that
> could process 580kpps with netfilter/conntrack turned off. Granted, the
> post noted that adding netfilter brought that down to 450kpps, and adding
> conntrack on top of that brought it down to 295kpps, but all three of
> those numbers are well over the claimed 100kpps.
Nonetheless, FreeBSD has some advantages. They achieved their results
using a fast forwarding path (enabled via sysctl) that processes
forwarded packets to completion entirely within the interrupt handler.
next prev parent reply other threads:[~2004-09-08 18:45 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 [this message]
2004-09-08 19:21 ` Tomasz Torcz
2004-09-08 18:56 ` Norbert van Nobelen
2004-09-08 19:01 ` Matt Kavanagh
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=413F525E.3010408@optonline.net \
--to=nbryant@optonline.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rcknl@qz.port5.com \
--cc=wstearns@pobox.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.