linux-kernel - Re: GT/s vs Gbps for PCIe bus speed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <adapr8p8zue.fsf@cisco.com>
Date:	Wed, 14 Oct 2009 13:50:17 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	ddutile@...hat.com
Cc:	Krzysztof Halasa <khc@...waw.pl>,
	Stefan Assmann <sassmann@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	kaneshige.kenji@...fujitsu.com, matthew@....cx
Subject: Re: GT/s vs Gbps for PCIe bus speed

FWIW, I think using the same nomenclature as the PCI-SIG documents is
probably the least confusing option.  Inventing our own terminology that
conflicts with the "upstream" PCI specs is just going to confuse things,
even if the Linux terminology is "better."  With that said:

>  	"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 */

it is the case that PCI-SIG uses "PCI-X" and "PCIe" rather than "PCIX"
and "PCI-E".  That naming would make sense to me as something to clean up.

The table of names also seems to be missing entries for PCI-X mode 1
with ECC, although I don't know if there ever was a system with a
device that actually used that mode.

 - R.
--
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/