From: Matthias Schniedermeyer <ms@citd.de>
To: Linda Walsh <lkml@tlinx.org>
Cc: Phillip Susi <psusi@ubuntu.com>,
util-linux@vger.kernel.org, Matthew Eaton <m.eaton82@gmail.com>,
Karel Zak <kzak@redhat.com>
Subject: Re: fdisk units size & disk manufacturers buying the standard
Date: Fri, 9 Jan 2015 10:16:34 +0100 [thread overview]
Message-ID: <20150109091634.GA18388@citd.de> (raw)
In-Reply-To: <54AF3ED8.2030508@tlinx.org>
On 08.01.2015 18:37, Linda Walsh wrote:
> Phillip Susi wrote:
> >>speed in Bytes varies by protocol. 1Gb-Base-T ethernet maxes out
> >>at a theoretical 125MB/s - divisible by 8. But 10Gb ethernet maxes
> >>out at 1000MB/s -- with 20% of its bandwidth going to protocol
> >>overhead.
> >
> >I'm not aware of any additional overhead that 10Gb ethernet has over
> >1Gb ethernet,
> ----
> See kernel messages for a 10b-T ethernet.
>
> [ 21.224641] ixgbe 0000:05:00.0: PCI Express bandwidth of 32GT/s available
> [ 21.224644] ixgbe 0000:05:00.0: (Speed:5.0GT/s, Width: x8, Encoding
> Loss:20%)
>
> I don't recall a 20% encoding loss in 1Gb or 100Mb ethernet and the kernel
> displays
> no such messages for the slower speed cards.
The message speaks about PCIe.
So the 40GBit/s (a.k.a. 40GT/s) is in effect 32GBit/s on the PCIe side.
5.0 GT/s = PCIe Gen. 2. PCIe Gen. 1 & 2 use 8b/10b encoding.
IOW for every 8 bits of payload 10 bits go ever the wire. This is 20%
the enconding loss the message speaks about.
PCIe Gen 3 (and 4) use an enhanced encoding called 128b/130b. IOW for
every 128 Bit of data 130Bits are send over the wire, so only 8GT/s
(instead of 10GT/s) were needed to (nearly) double the effective
datarate in Gen 3.
See:
http://en.wikipedia.org/wiki/PCI_Express
Which still leaves well enough headroom to get the 10Git/s for the
ethernet-connection across.
--
Matthias
next prev parent reply other threads:[~2015-01-09 9:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 0:19 fdisk units size Matthew Eaton
2014-12-04 13:00 ` Karel Zak
2014-12-04 14:14 ` Martin Steigerwald
2014-12-04 16:59 ` Matthew Eaton
2014-12-08 21:35 ` fdisk units size & disk manufacturers buying the standard Linda Walsh
2014-12-08 22:53 ` Felix Miata
2014-12-09 21:17 ` Dale R. Worley
2015-01-05 22:17 ` Phillip Susi
2015-01-08 0:21 ` Linda Walsh
2015-01-08 3:56 ` Phillip Susi
2015-01-08 6:31 ` Peter Cordes
2015-01-09 2:37 ` Linda Walsh
2015-01-09 9:16 ` Matthias Schniedermeyer [this message]
2015-01-09 14:59 ` Phillip Susi
2015-01-10 0:29 ` Linda Walsh
2015-01-12 18:50 ` Phillip Susi
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=20150109091634.GA18388@citd.de \
--to=ms@citd.de \
--cc=kzak@redhat.com \
--cc=lkml@tlinx.org \
--cc=m.eaton82@gmail.com \
--cc=psusi@ubuntu.com \
--cc=util-linux@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.