From: Andreas John <lists@aj.net-lab.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Linux router performance
Date: Wed, 31 May 2006 20:27:10 +0000 [thread overview]
Message-ID: <447DFC1E.60007@aj.net-lab.net> (raw)
In-Reply-To: <004e01c684dc$3dfc3c10$303d5854@cttc.es>
Hi,
Maybe:
Khan, Sohel; Waheed, Abdul (2003): High Performance Routing on
PCshttp://www.ccse.kfupm.edu.sa/~sohel/networking/references/Routing.pdf
A rule of thumb:
- with current COTS hardware and (standard) PCI Bus, you can reach the
maximum of the PCI bus bandwidth. That's 1 GB/s, e.h. two NICs with 500
Meg/s each ( one in and one out )
- with PCI-X and in the future PCI-express you'll for sure be able to
reach more performance. I didnt find a sponsor for a test-lab yet :)
- in DoS secnarios it may get worse :/ I heavily depends on driver type
(polling and NAPI preferred). The problem with the performace is
_always_ the number of interrupts, nothing else is a bottleneck (well,
we didn't talk about thousands of iptables rules yet, but you ask for a
'maximum').
- The question you have to ask in high-performance scenarios is not
"MBit/s" but MPPS (megapackets per seconds). FreeBSD and Linux broke the
1 MPPS barrier some time ago (on dual xeons).
rgds,
Andreas
Fermín Galán Márquez wrote:
> Hi,
>
> I wonder about the performance of a Linux box used as router (I guest I'm
> not the first :). Althought I know it mainly depends on the hardware, I'm
> trying to find some references on the topic or comparations with other
> routing solutions (FreeBSD box used as router, Cisco, etc). For example,
> http://facweb.cti.depaul.edu/jyu/Publications/Yu-Linux-TSM2004.pdf
> (althought is related with Linux-briding more than with Linux-routing) shows
> in Figure 14 that with an AMD Duron 1.3GHz 512M RAM a throughput of 90 Mbps
> can be achieved.
>
> Anybody knows any other similar analysis, please?
>
> Best regards,
>
> --------------------
> Fermín Galán Márquez
> CTTC - Centre Tecnològic de Telecomunicacions de Catalunya
> Parc Mediterrani de la Tecnologia, Av. del Canal Olímpic s/n, 08860
> Castelldefels, Spain
> Room 1.02
> Tel : +34 93 645 29 12
> Fax : +34 93 645 29 01
> Email address: fermin.galan@cttc.es
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-05-31 20:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 18:01 [LARTC] Linux router performance Fermín Galán Márquez
2006-05-31 20:27 ` Andreas John [this message]
2006-05-31 23:24 ` Carl-Daniel Hailfinger
2006-06-01 0:34 ` Damjan
2006-06-01 0:44 ` Carl-Daniel Hailfinger
2006-06-01 1:59 ` Alexander Samad
2006-06-01 2:03 ` Carl-Daniel Hailfinger
2006-06-01 2:21 ` Alexander Samad
2006-06-01 4:52 ` Carl-Daniel Hailfinger
2006-06-01 8:46 ` Andrew Lyon
2006-06-01 11:23 ` Ronny Aasen
2006-06-01 11:46 ` Carl-Daniel Hailfinger
2006-06-01 20:33 ` Jesper Dangaard Brouer
2006-06-10 6:45 ` S Mohan
2006-06-16 7:52 ` Tomas Bonnedahl
2006-06-16 8:23 ` [LARTC] Linux router performance (fwd) Jesper Dangaard Brouer
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=447DFC1E.60007@aj.net-lab.net \
--to=lists@aj.net-lab.net \
--cc=lartc@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.