public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Dutile <ddutile@redhat.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: Krzysztof Halasa <khc@pm.waw.pl>,
	Stefan Assmann <sassmann@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	kaneshige.kenji@jp.fujitsu.com, matthew@wil.cx
Subject: Re: GT/s vs Gbps for PCIe bus speed
Date: Thu, 15 Oct 2009 10:05:27 -0400	[thread overview]
Message-ID: <4AD72C27.60006@redhat.com> (raw)
In-Reply-To: <adabpk985q9.fsf@cisco.com>

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


  reply	other threads:[~2009-10-15 14:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14  8:42 GT/s vs Gbps for PCIe bus speed Stefan Assmann
2009-10-14 18:51 ` 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 [this message]
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=4AD72C27.60006@redhat.com \
    --to=ddutile@redhat.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=rdreier@cisco.com \
    --cc=sassmann@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox