All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Assmann <sassmann@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	kaneshige.kenji@jp.fujitsu.com, matthew@wil.cx,
	ddutile@redhat.com
Subject: GT/s vs Gbps for PCIe bus speed
Date: Wed, 14 Oct 2009 10:42:22 +0200	[thread overview]
Message-ID: <4AD58EEE.4070405@redhat.com> (raw)

Hi all,

I'm really confused about GT/s¹ vs Gbps². The PCIe 2.0 Base Spec (rev 0.9)
on page 34, section 1.2 speaks of "Signaling rate - [...] For the first
generation of PCI Express technology, there is only one signaling rate
defined, which provides an effective 2.5 Gigabits/second/Lane/direction
of raw bandwidth." but later in the document it purely speaks of 2.5
GT/s.

If I understand this correctly it means the following:
PCIe has a raw bandwidth of 2.5 Gbps (or 5.0 Gbps, whatever) but because
of the "8b/10b" encoding the effective bit rate is only
2.5 Gbps * (8/10). So it's called 2.5 GT/s to explicitly say this is raw
bandwidth.

IMHO this is rather confusing, as most people don't know what GT/s means.

So I'd suggest the following change:

diff --git a/drivers/pci/hotplug/pci_hotplug_core.c b/drivers/pci/hotplug/pci_hotplug_core.c
index 0325d98..75ef3d7 100644
--- a/drivers/pci/hotplug/pci_hotplug_core.c
+++ b/drivers/pci/hotplug/pci_hotplug_core.c
@@ -86,8 +86,8 @@ static char *pci_bus_speed_strings[] = {
 	"66 MHz PCIX 533",	/* 0x11 */
 	"100 MHz PCIX 533",	/* 0x12 */
 	"133 MHz PCIX 533",	/* 0x13 */
-	"2.5 GT/s PCI-E",	/* 0x14 */
-	"5.0 GT/s PCI-E",	/* 0x15 */
+	"2.5 Gbps PCI-E",	/* 0x14 */
+	"5.0 Gbps PCI-E",	/* 0x15 */
 };

 #ifdef CONFIG_HOTPLUG_PCI_CPCI


¹ Gigatransfers/second
² Gigabits/second

  Stefan
--
Stefan Assmann         | Red Hat GmbH
Software Engineer      | Otto-Hahn-Strasse 20, 85609 Dornach
                       | HR: Amtsgericht Muenchen HRB 153243
                       | GF: Brendan Lane, Charlie Peters,
sassmann at redhat.com |     Michael Cunningham, Charles Cachera

             reply	other threads:[~2009-10-14  8:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14  8:42 Stefan Assmann [this message]
2009-10-14 18:51 ` GT/s vs Gbps for PCIe bus speed Krzysztof Halasa
2009-10-14 19:49   ` Don Dutile
2009-10-14 20:50     ` Roland Dreier
2009-10-15  7:32       ` Kenji Kaneshige
2009-10-14 21:33     ` Krzysztof Halasa
2009-10-14 22:51       ` Don Dutile
2009-10-15  7:40         ` Roland Dreier
2009-10-15 14:05           ` Don Dutile
2009-10-15 17:58         ` Krzysztof Halasa

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=4AD58EEE.4070405@redhat.com \
    --to=sassmann@redhat.com \
    --cc=ddutile@redhat.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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.