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]

Date:	Thu, 15 Oct 2009 00:40:46 -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

 > Yeah, the std nomenclature is PCI-e not PCI-E.

To be pedantic: "PCIe" without the hyphen is correct, cf
http://www.pcisig.com/specifications/pciexpress/ (the web page, not any
member-only specs) -- "PCIe" is used many times there.

 > Again, trying to generate output that relates
 > to what devices are spec to run at: 2.5GHz or 5.0GHz links.

But the spec does not talk about rates in GHz but rather GT/s (since
PCIe is not clocked but rather uses a recovered embedded clock).
Matching the terminology of the PCIe spec by using GT/s really seems
best in terms of clarity, and describes the situation most exactly,
since by using GT/s one also sidesteps the issue of having the data rate
depend on the link width.

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