[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m3ljjdstbb.fsf@intrepid.localdomain>
Date: Wed, 14 Oct 2009 20:51:04 +0200
From: Krzysztof Halasa <khc@...waw.pl>
To: Stefan Assmann <sassmann@...hat.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
kaneshige.kenji@...fujitsu.com, matthew@....cx, ddutile@...hat.com
Subject: Re: GT/s vs Gbps for PCIe bus speed
Stefan Assmann <sassmann@...hat.com> writes:
> IMHO this is rather confusing, as most people don't know what GT/s means.
It's trivial to look it up, isn't it?
> So I'd suggest the following change:
>
> --- 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 */
Isn't it like calling 100BASE-TX a 125 Mb/s? _That_ would be confusing.
BTW PCI-E can be multi-lane so Mb/s (and even MB/s) don't make sense.
I guess many people don't know what a MHz is either but we don't say
133 MHz = 133 Mbps.
--
Krzysztof Halasa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists