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: <4AD72C27.60006@redhat.com>
Date:	Thu, 15 Oct 2009 10:05:27 -0400
From:	Don Dutile <ddutile@...hat.com>
To:	Roland Dreier <rdreier@...co.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

Roland Dreier wrote:
>  > 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.
> 
agreed.

>  > 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).
Yes, it does in section 2.1, page 38 of base spec:
   Signaling rate – Once initialized, each Link must only operate at one of the supported signaling
   levels. 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.
   The second generation provides an effective 5.0 Gigabits/second/Lane/direction of raw
   bandwidth. The data rate is expected to increase with technology advances in the future.

Additionally, the original specs listed the Link speeds in the Link Capabilities
register as Gb/s; this is also reflected in MindShare's PCI Express System Architecture
book (3rd edition; I'm curious to find out if the 4th edition updated this area
to the GT/s terminology).

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

So, the original spec (and for those that worked on it originally), the
link speeds were stated in Gb/s.
If GT/s will be the nomenclature used by PCIe vendors
when they have varying speed devices, then I agree, use the GT/s terminology.
Doing a number of varying web searches, it appears the hw vendors
are avoiding which to use: T/s or b/s by using "2.5G" & "5.0G"
sometimes prefixing with "Gen1-" & "Gen2-" respectively.

Maybe we should take a hint from the hw folks and drop the use of "T/s" or "b/s"
and just output "2.5G", "5.0G".... and when it gets here "8.0G".

cheers... Don

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