From: Robert Olsson <Robert.Olsson@data.slu.se>
To: Mårten_Wikström <Marten.Wikstrom@framfab.se>
Cc: Rik van Riel <riel@conectiva.com.br>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com
Subject: Re: How to optimize routing performance
Date: Thu, 15 Mar 2001 15:19:23 +0100 (CET) [thread overview]
Message-ID: <15024.53099.41814.716733@robur.slu.se> (raw)
Rik van Riel writes:
> On Thu, 15 Mar 2001, [ISO-8859-1] Mårten Wikström wrote:
>
> > I've performed a test on the routing capacity of a Linux 2.4.2 box
> > versus a FreeBSD 4.2 box. I used two Pentium Pro 200Mhz computers with
> > 64Mb memory, and two DEC 100Mbit ethernet cards. I used a Smartbits
> > test-tool to measure the packet throughput and the packet size was set
> > to 64 bytes. Linux dropped no packets up to about 27000 packets/s, but
> > then it started to drop packets at higher rates. Worse yet, the output
> > rate actually decreased, so at the input rate of 40000 packets/s
It is a known problem yes. And just as Rik says its has been adressed
in 2.1.x by Alexey for first time.
> > almost no packets got through. The behaviour of FreeBSD was different,
> > it showed a steadily increased output rate up to about 70000 packets/s
> > before the output rate decreased. (Then the output rate was apprx.
> > 40000 packets/s).
>
> > So, my question is: are these figures true, or is it possible to
> > optimize the kernel somehow? The only changes I have made to the
> > kernel config was to disable advanced routing.
>
> There are some flow control options in the kernel which should
> help. From your description, it looks like they aren't enabled
> by default ...
CONFIG_NET_HW_FLOWCONTROL enables kernel code for it. But device
drivers has to have support for it. But unfortunely very few drivers
has support for it.
Also we done experiments were we move the device RX processing to
SoftIRQ rather than IRQ. With this RX is in better balance with
other kernel tasks and TX. Under very high load and under DoS
attacks the system is now manageable. It's in practical use already.
> At the NordU/USENIX conference in Stockholm (this february) I
> saw a nice presentation on the flow control code in the Linux
> networking code and how it improved networking performance.
> I'm pretty convinced that flow control _should_ be saving your
> system in this case.
Thanks Rik.
This is work/experiments by Jamal and me with support from Gurus. :-)
Jamal did this presentation at OLS 2000. At NordU/USENIX I gave an
updated presentation of it. The presentation is not yet available form
the usenix webb I think.
It can ftp from robur.slu.se:
/pub/Linux/tmp/FF-NordUSENIX.pdf or .ps
In summary Linux is very decent router. Wire speed small packets
@ 100 Mbps and capable of Gigabit routing (1440 pkts tested)
we used.
Also if people are interested we have done profiling on a Linux
production router with full BGP at pretty loaded site. This to
give us costs for route lookup, skb malloc/free, interrupts etc.
http://Linux/net-development/experiments/010313
I'm on netdev but not the kernel list.
Cheers.
--ro
next prev reply other threads:[~2001-03-15 14:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-16 0:38 Rik van Riel
2001-03-15 14:19 ` Robert Olsson [this message]
2001-03-15 18:45 ` Robert Olsson
2001-03-15 19:30 ` Jonathan Morton
2001-03-15 19:54 ` Robert Olsson
2001-03-15 21:01 ` jamal
-- strict thread matches above, loose matches on Subject: below --
2001-03-16 7:21 Mårten Wikström
2001-03-16 8:08 ` Martin Josefsson
[not found] <3AB12640.79E7B4FB@colorfullife.com>
2001-03-15 21:39 ` Robert Olsson
2001-03-15 20:16 Jonathan Earle
2001-03-15 7:23 Mårten Wikström
2001-03-15 12:32 ` Rik van Riel
2001-03-15 16:20 ` Martin Josefsson
2001-03-15 18:09 ` J Sloan
2001-03-16 2:05 ` Rik van Riel
2001-03-15 19:17 ` J Sloan
2001-03-15 19:36 ` Gregory Maxwell
2001-03-15 19:45 ` J Sloan
2001-03-15 19:44 ` Mike Kravetz
2001-03-16 2:35 ` Rik van Riel
2001-03-15 19:28 ` J Sloan
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=15024.53099.41814.716733@robur.slu.se \
--to=robert.olsson@data.slu.se \
--cc=Marten.Wikstrom@framfab.se \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=riel@conectiva.com.br \
/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
all inboxes | Powered by JetHome®