From: Tomasz Torcz <zdzichu@irc.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux Routing Performance inferior?
Date: Wed, 8 Sep 2004 21:21:18 +0200 [thread overview]
Message-ID: <20040908192118.GH7736@irc.pl> (raw)
In-Reply-To: <413F525E.3010408@optonline.net>
On Wed, Sep 08, 2004 at 02:41:34PM -0400, Nathan Bryant wrote:
> >>"FreeBSD (5.x) can route 1Mpps on a 2.8G Xeon while
> >>Linux can't do much more than 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.
I've already posted presentation about those features (*) to netdev.
Some ideas looks interesting enough to be implemented in Linux.
* http://people.freebsd.org/~andre/FreeBSD-5.3-Networking.pdf
--
Tomasz Torcz To co nierealne - tutaj jest normalne.
zdzichu@irc.-nie.spam-.pl Ziomale na życie mają tu patenty specjalne.
next prev parent reply other threads:[~2004-09-08 19:22 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 [this message]
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=20040908192118.GH7736@irc.pl \
--to=zdzichu@irc.pl \
--cc=linux-kernel@vger.kernel.org \
/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.