The Power of PCIe in Performance-based FPGA World

Understanding High speed serial data transfer

Vatsal Choksi, Applications Engineer
Like(2)  Comments  (0)

In today's world, when the entire computing industry is talking about high-performance and high-speed applications using FPGAs, just what are the factors that can assure such performance and speed? The value and success of today’s high performance computing applications in the areas of DNA Sequencing, High Frequency Trading (HFT) and Encryption/Decryption are predicated upon how fast data can be transferred from device to device.

 

In this blog, I am going to discuss about the most popular data transfer protocol called PCIe. Why do most companies depend upon it to get best data throughput? How does it differ from PCI? How is it used in an FPGA? What is the future of PCIe? Let’s find out!

 

The PCI bus was developed for high parallel data transfer applications. But over time, the demand for more devices and I/Os increased. With that, PCI bus eventually turned out to be slow, and something better with a different bus topology was required.

 

Entered PCIe, it’s a complete overhaul from the previous PCI bus protocol. There are different ways through which PCIe differs from PCI. Firstly, it has switch architecture while PCI has a multi-drop bus structure. Another major difference is the fact that PCIe is a device sending data packets to another device. Take a look at Figure 1 shown below - a packet that comprises a Header and a Payload. The Header carries control information while the Payload has the data to be transferred from one device to another. This is similar to networking concepts. A major disadvantage of using PCI was that there were high chances of data inaccuracies (if parallel buses would have stale data because of bus capacitance affecting one another. PCIe completely gets rid of that issue by providing the centralized switch architecture. PCIe also has a CRC error detecting code layer as part of it. The receiving device makes sure that the error detecting code is correct in order to measure the credibility of the data received. PCIe is also pluggable – meaning devices can be added or removed from the system while it is running

 

Figure 1: PCIe Top Level Structure

 

Now, let’s understand the multiple layers of PCIe. PCIe is known as a protocol as it follows a different set of rules between the sending and receiving party. PCIe is made up of four different layers: the Physical Layer, the Link Layer, the Transaction Layer, and the Software Layer.

 

The Physical Layer is architecturally the lowest layer. It is used to move data bits from sender to receiver over simplex or duplex lanes. The number of lanes in each direction (sender and receiver) is the same. Basically, the Physical Layer deals with bit-to-bit transmissions.

 

The Link Layer deals with packet transmissions. The Header and Payload given to the Link Layer by the Transaction Layer are adjoined by a random sequence number and an error correcting code also known as CRC. It is generated by performing random algorithm based logic calculations. At the time the packet is received, the receiver performs the same computation on the Header and the Payload. Thus, it compares the data. The data received must agree with the data sent. The Transaction Layer handles the bus actions.

 

The Software Layer interfaces the PCIe system architecture to the host operating system. The Software Layer of PCIe provides the backward compatibility that helps maintain the synchronization between different systems.

 

PCIe is now quite common in FPGA boards for various high-performance computing applications. For example, in data centers, it is important to maximize the performance while minimizing the power consumption. Today, FPGA based acceleration platforms include PCIe based programmable acceleration cards such as our HES-XCVU9P-QDR for HFT applications.

 

HES-XCUV9P-QDR HFT Board

Figure 2: HES-XCUV9P-QDR HFT Board

 

In order to achieve the highest performance and throughput, PCIe IP blocks are generally developed using RTL. Since PCIe is expandable various IP vendors are able to manipulate the system architecture of PCIe and optimize them based on application’s specific needs. There are several IP vendors who develop PCIe IP blocks in order to achieve max throughput, including our partner Northwest Logic - together we delivered an FPGA board based on Ultrascale+ with PCIe Gen 3 solution and high-performance-gather DMA support.

Now, debugging the hardware on FPGA using an oscilloscope will take a lot of time so the best way to debug your design is to use a high-performance simulator. You would need advanced debugging tools such as Advanced Dataflow, Xtrace to find out unknown values and Waveform Viewer. Check out Aldec’s high performance advanced verification simulator Riviera-PRO.

 

While PCIe applications are quite common due to scalability and flexibility, is PCIe replaceable? Yes it is! There are many graphical game developers who are always looking to design games and applications more and more realistic. That can be achieved only and only by passing more data from their applications to the VR headset. That requires faster data interfaces. Because of these reasons, although PCIe offers great speed, several other data transfer protocols and standards are considered as well. There are already other interface standards in the market being looked at by the industry. RapidIO, HyperTransport, Mobile Industry Processor Interface are such examples, and wide adoption of these standards will speed up the innovations in the computing industry. These new standards will of course require new hardware or even ASICs that are yet to be developed. Hence PCIe will lead for some more time.

Vatsal provides technical support for Aldec’s software products such as Active-HDL and Riviera-PRO. He is proficient in FPGA/ASIC digital design and verification.As a technical support engineer, Vatsal has deep understanding of verification languages such VHDL, Verilog/SystemVerilog, SystemC and methodologies such as OSVVM, UVVM and UVM. Vatsal received his master’s degree in the field of Electrical and Electronics Engineering from California State University Sacramento in year 2015. His desire and passion is to know and learn more about design and verification that makes him suitable at solving complex verification issues.

  • Products:
  • Riviera-PRO
  • Advanced Verification,
  • HES-DVM
  • ハードウェア・アシステッド・ベリフィケーション

Comments

Ask Us a Question
x
Ask Us a Question
x
Captcha ImageReload Captcha
Incorrect data entered.
Thank you! Your question has been submitted. Please allow 1-3 business days for someone to respond to your question.
Internal error occurred. Your question was not submitted. Please contact us using Feedback form.
We use cookies to ensure we give you the best user experience and to provide you with content we believe will be of relevance to you. If you continue to use our site, you consent to our use of cookies. A detailed overview on the use of cookies and other website information is located in our Privacy Policy.