All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mohan Sundaram <smohan@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] New hardware
Date: Tue, 22 Aug 2006 02:21:24 +0000	[thread overview]
Message-ID: <44EA6754.6000909@vsnl.com> (raw)
In-Reply-To: <1156175178.44e9d54a18bd1@www.inbox.lv>

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.

Got a raw forwarding performance of 800Kpps for 64B packets. This beat a 
CISCO 3845 which gave 600Kpps.

Raw forwarding is one measure though it is not the end-all.

Mohan
Marek Kierdelewicz wrote:
>> Hi! 
> 
> Hi
> 
>> reason of hardware upgrade is growing up number of users, also we are
>> planning to increase upstream link from 100 Mbit/s to 1 Gbit/s.
> 
> If you want to move around 1Gbit/s you need PCI-X or PCI-E network
> interfaces (PCI bus would be a bottleneck).
> 
>> 1) Server based router (with dual core Xeon CPU) 
> 
> I've been using for some time now router with 2xsingle-core Xeon CPU
> for servicing 2k+ users. It works well. 
> 
>> 2) Desktop based router (with newest Intel Core 2 Duo CPU) 
> 
> Did't have a pleasure. I'd like to hear some opinions on that one too.
> 
>> 3) what about AMD (I have no personal experience with them)? 
> 
> I'm trying to use unorthodox hardware setup for fast router:
> 
> Dual core AMD64
> desktop motherboard with 2xPCIe x16 slots (SLI capable motherboard)
> two PCIe x4 intel E1000 Server network adapters
> 
> Preliminary tests look promising. Network adapters mentioned above
> should in theory do better then previous PCI-X network adapters.
> 
>> As I know, 64-bit architecture in router specific tasks doesn&rsquo;t
>> give any performance boost? Maybe there are some other nuances that I
>> need to know (kernel hacking, hardware hints)? 
> 
> I think 64-bit architectures can do much better then 32-bit ones... at
> least on 64-bit kernel.
> 
>> I&rsquo;m going to use standard Intel E1000 NIC for 1 Gbit/s speed
>> line, is it a good choice? 
> 
> Best choice as far as I know. Anyone would sugest something else?
> 
> Regards,

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-08-22  2: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 [this message]
2006-08-23  7:51 ` Marek Kierdelewicz
2006-08-23  8:17 ` Mohan Sundaram
2006-08-23  8:21 ` Mohan Sundaram

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=44EA6754.6000909@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 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.