为什么有这么多不同类型的端口用于高速串行通信

所有这些类型的通信都使用高速串行I / O.
通信协议有很多层。
最低级别是物理层。
这里，确定连接类型（铜或光），电压标准（即CML）是铜，以及比特率（1Gbps，2.5Gbps，3.25Gbps）。
GTX / GTP（和其他）可用于所有这些物理层（尽管光学层需要光学收发器）。
在那之后，还有其他的事情。
什么是编码方案 
-  8b10b 
-  64b66b 
-  64b67b 
-  sonet争抢
然后通道绑定 
-  1个链接，2个链接，4个链接
然后是数据特征 
- 打包 
- 基于框架
之后，用于成帧，同步，chanel绑定等的符号序列......
一旦你完成了这些（并且还有更多级别），这些接口中的每一个都可能非常不同。
我们使用不同电缆和连接器的原因正是因为这个原因。
我们希望确保没有人将SATA驱动器插入以太网端口并期望它能够正常工作！
Avrum



以下为原文

All of these types of communication use the High Speed Serial I/O.
 
There are many layers to communication protocols.
 
The lowest level is the Physical layer. Here, things such as the type of connection (copper or optical), the voltage standard (i.e. CML) it is copper, and the bit rate are determined (1Gbps, 2.5Gbps, 3.25Gbps). The GTX/GTP (and others) can be used for all these physical layers (though the optical ones need an optical transceiver).
 
After that, there are other things. What is the encoding scheme
  - 8b10b
  - 64b66b
  - 64b67b
  - sonet scrambling

Then channel bonding
  - 1 link, 2 links, 4links
 
Then there are the data characteristics
  - packetized
  - frame based
 
After that, the sequence of symbols used for framing, sync, chanel bonding, etc...
 
Once you are through with these (and there are many more levels above this), each of these interfaces can be VERY different.
 
The reason we use different cables and connecters is precisely because of this. We want to make sure that no one plugs a SATA drive into an ethernet port and expects it to work!
 
Avrum

非常感谢，Avrum。
我想我可以理解你的解释：如果所有接口都使用相同的端口，这就难以区分不同的接口。
人们无法通过外观来区分接口，因为它们都具有相同的端口，并且有人可能将以太网端口连接到SATA端口并期望它可以工作。



以下为原文

Thanks very much, Avrum. I think I can understand your explanation as this: if all interfaces use same port, this brings difficults to distinguish the differnt interface. People can not distinguish the interface through apperance because all of them has same port, and someone may connect a Ethernet port to a SATA port and expect it works.
 
 

我还有两个问题：
1.每个协议都有特定的端口和电缆吗？
例如。
Aurora协议的电缆和端口是什么？
2.在您的线程中，除了PHY之外，您还提到需要考虑的其他事项包括：编码方案，通道绑定和数据特征。
所有这些都是在协议中确定的吗？
我的意思是：例如
Aurora或以太网协议确定它们的ownencoding方案，通道绑定和数据特征，对吧？
非常感谢。



以下为原文

I have another two questions:
 
1. Does every protocol has specific port and cable? E.g. what is the cable and port for Aurora protocol?
2. In your thread, you mentioned besides PHY there are other things need to consider include: encoding scheme, channel bonding, and data characteristics. Are all of them determined in protocol? I mean: e.g. Aurora or Ethernet protocol determine their own encoding scheme, channel bonding, and data characteristics, right?
 

Thanks very much.