netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Raz <raziebe@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: what is the expeted performance from a dual port 10G card ?
Date: Sat, 29 Nov 2008 17:34:43 +0000	[thread overview]
Message-ID: <20081129173442.GI32518@solarflare.com> (raw)
In-Reply-To: <5d96567b0811290010r641388b7w179bc4af26bbf103@mail.gmail.com>

Raz wrote:
> PCI Encoding overhead is 8 bits /10 bits . so 16Gbps supposed to be
> the practical limit.

The 8b10 encoding is already accounted for in the 2.5 Gbps figure;
the raw bit rate is 3.125 Gbps.

I'm thinking about the transaction layer overhead.  Since PCI Express
has few side-band signals there is a protocol a little like TCP running
over the link, which adds a header to each request or response packet
(TLP).  The maximum TLP size is usually quite small so the header
accounts for a fair proportion of the link bandwidth.

> I still lack 3 Gbps in the Intel case. where are they ?

That's for Intel to answer.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

  reply	other threads:[~2008-11-29 17:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28 13:11 what is the expeted performance from a dual port 10G card ? Raz
2008-11-28 13:54 ` Ben Hutchings
2008-11-29  8:10   ` Raz
2008-11-29 17:34     ` Ben Hutchings [this message]
2008-11-29 22:46       ` Roland Dreier
2008-11-30  2:55         ` Trent Piepho
2008-11-30  7:25           ` Raz
2008-11-30 17:31             ` Roland Dreier
2008-12-01 18:16         ` Rick Jones
2008-11-29  6:30 ` Divy Le Ray
2008-11-29  8:11   ` Raz
2008-12-01 15:17 ` Christoph Lameter

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=20081129173442.GI32518@solarflare.com \
    --to=bhutchings@solarflare.com \
    --cc=netdev@vger.kernel.org \
    --cc=raziebe@gmail.com \
    /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).