Managing NVME Verification Complexity
November 6, 2019
From inception, NVMe was designed to support multiple hosts accessing shared media. Early implementation included PCIe in-the-box devices such as Endpoint(EP), Root complex(RC) and Root complex integrated endpoint(RCiEP); over time, Cloud and Storage infrastructure created a need for remote storage.
NVMe implementation can address space occupied by both SATA point-to-point architecture and SAS. Successful adoption in both spaces is due to the promise of low latency and a common interface for storage, regardless of location. Though the verification challenges in these two use cases are similar, they still require a different thought process.
To read the full article, click here
Related Semiconductor IP
- NVMe Streamer
- EXFAT IP Soft Core for NVMe
- FAT32 IP Soft Core for NVMe
- ARTIX Ultra Scale Plus NVME HOST IP – Gen4
- Kintex Ultra Scale Plus NVMe Host IP
Related Blogs
- Keeping up with NVMe Technology Through Compliance Testing and Pre-Production Verification
- Navigating the Complexity of Address Translation Verification in PCI Express 6.0
- NVMe storage-optimized PCIe interface gets an Interoperability Lab at University of New Hampshire
- Expansion of NVMe Support Signals Growth
Latest Blogs
- CDM Dependence on Device Capacitance
- What the Cyber Resilience Act means for the future of chip design
- When Your IP Vendor Has Operated 150,000 Base Stations: Introducing Viettel Semiconductor
- Relationship between architecture and validation in system design
- The Post-Quantum Cryptography Mandate: Building Cryptographically Agile Systems for the Quantum Era