From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] myricom 10 gigabit ethernet
Date: Sat, 7 Apr 2007 17:13:02 -0400 [thread overview]
Message-ID: <fdf683046fa1a9c71171b56c5581cb38@coraid.com> (raw)
In-Reply-To: <4617FEB3.6080203@conducive.org>
> erik quanstrom wrote:
>> this is not correct. please read http://en.wikipedia.org/wiki/Peripheral_Component_Interconnect
>> even at 33 mhz, pci has 133MB/s of bandwidth. gbe uses about 112MB/s.
>>
>> although there are some lower standards defined, pci-x has a practical base
>> frequency of 133Mhz * 64 bits which is over 1GB/s.
>>
>> pcie is (8/10)*2.5gbit bidirectional per lane. just 1 lane is required for gbe.
>>
>
> Do you suppose there is nothing else wanting to 'do work' on, or use that bus?
> Or place 'non-bus' demands on the rest of the system?
pci-[ex] "busses" aren't shared resources. they are point-to-point links. there is
no contention on a pci-[ex] link.
also, even modestly modern machines have multiple pci busses. my 997Mhz pIII
hand-me-down has 3 and my 450Mhz 440gx fileserver has 2.
>
> 4 x Gig-E is about the most you can keep up with and still do 'useful work',
> even with twin dual-core AMD.
>
> - unless you have the cash for Many-MP IBM Power5 / Power6 ?
>
> Everyone wants to add-up the 'best case' burst rates for every component.
do you have any data to back this up?
> Reality is to take the worst-case, then focus on fixing those bottlenecks first.
>
> As usual. the main one is *money*...
isn't that too easy? i think that if i take that attitude as a software engineer,
i won't look at what my software's doing and work to make it better.
i believe the fundamental bottleneck is ideas. without a good idea, unlimited
wherewithall buys nothing.
- erik
next prev parent reply other threads:[~2007-04-07 21:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-07 16:03 matt
2007-04-07 16:18 ` Robert Sherwood
2007-04-07 16:58 ` matt
2007-04-07 17:00 ` Paweł Lasek
2007-04-07 17:03 ` W B Hacker
2007-04-07 18:27 ` erik quanstrom
2007-04-07 20:27 ` W B Hacker
2007-04-07 21:13 ` erik quanstrom [this message]
2007-04-07 23:15 ` W B Hacker
2007-04-07 17:52 ` erik quanstrom
2007-04-07 17:58 ` erik quanstrom
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=fdf683046fa1a9c71171b56c5581cb38@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).