From: Roland Dreier <rdreier@cisco.com>
To: ddutile@redhat.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 00:40:46 -0700 [thread overview]
Message-ID: <adabpk985q9.fsf@cisco.com> (raw)
In-Reply-To: <4AD655E1.7080005@redhat.com> (Don Dutile's message of "Wed, 14 Oct 2009 18:51:13 -0400")
> 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.
next prev parent reply other threads:[~2009-10-15 7:41 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 [this message]
2009-10-15 14:05 ` Don Dutile
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=adabpk985q9.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.