From: Mohan Sundaram <smohan@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] New hardware
Date: Wed, 23 Aug 2006 08:21:19 +0000 [thread overview]
Message-ID: <44EC0D2F.7050306@vsnl.com> (raw)
In-Reply-To: <1156175178.44e9d54a18bd1@www.inbox.lv>
Marek Kierdelewicz wrote:
> Hi there,
>
>> I used a SunFire x2100 which has 2 Ghz Opteron and PCI-Xpress slot
>> into which I plugged in a dual port gigE Intel PCI-Xpress card.
>
> What was the software configuration of this host? What kernel
> have you used for the test (compiled for x86 or amd64; dual-core
> aware sheduler or not).
>
> Out of the curiosity ... dual port nic generates one interrupt or two
> per port? I asume the first is more probable. This leads to another
> question - has interrupt been balanced between cores?
>
>> Got a raw forwarding performance of 800Kpps for 64B packets. This
>> beat a CISCO 3845 which gave 600Kpps.
>
> Thanks for the input :).
>
> Right now my production border router (BGP+some firewall rules+some QoS,
> vlans @ P4 3GHz Linux 2.6, 2xBroadcom PCI-X, 1xIntel E1000 PCI-X) is 91%
> saturated (CPU) at peek hours and during the time it forwards 344,8Kpps
> with avg. packet sized 69 bytes.
>
> I'll try to determine raw forwarding performance when box goes out
> of production env, so we'll have a clear comparison picture.
>
> regards,
The beauty was the price. $725 for the SUN hardware and $200 for the NIC
card. The CISCO 3845 would cost 9K street minimum.
Mohan
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-08-23 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 15:46 [LARTC] New hardware Jurijs Petrovs
2006-08-21 16:16 ` Marek Kierdelewicz
2006-08-22 2:21 ` Mohan Sundaram
2006-08-23 7:51 ` Marek Kierdelewicz
2006-08-23 8:17 ` Mohan Sundaram
2006-08-23 8:21 ` Mohan Sundaram [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=44EC0D2F.7050306@vsnl.com \
--to=smohan@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox