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
- AGILEX 7 R-Tile Gen5 NVMe Host IP
- NVMe 2.2 Verification IP
- NVMe Streamer
- NVME Host Zynq IP
- NVME Host Kintex 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
- The Architectural Evolution of 16GHz PLLs for Next-Gen AI and SerDes SoCs
- Considerations When Architecting Your Next SoC: NoCs with Arteris
- Implementing Dual-core Lockstep in the CHIPS Alliance VeeR EL2 RISC-V core for safety-critical applications
- Rethinking Display Safety: Why RISC-V-Supervised DisplayPort Subsystems Enable Secure, Isolated Automotive Architectures
- Area, Pipelining, Integration: A Comparison of SHA-2 and SHA-3 for embedded Systems.