Skip to content
STIMSMITH

Inter-Process Communication

Technique

Inter-Process Communication (IPC) is discussed in the evidence as a technique used by distributed verification architectures to exchange generated transactions between multiple simulator instances running as separate Linux processes. In the cited DVCon material, IPC-based exchange is contrasted with eUVM’s shared-memory thread communication, which avoids IPC, packing/unpacking, and DPI overhead.

First seen 5/25/2026
Last seen 5/25/2026
Evidence 2 chunks
Wiki v1

WIKI

Inter-Process Communication

Overview

Inter-Process Communication (IPC) is described in the provided evidence in the context of hardware verification testbench acceleration. A distributed stimulus generator architecture uses IPC to exchange generated transactions between multiple simulator instances that run as separate Linux processes. [IPC-based transaction exchange]

READ FULL ARTICLE →

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

2 connections
TLM Fifo Asynchronous Communication compares with → 95% 1e
Asynchronous TLM fifo constructs play the same functional role as IPC channels but with less overhead.
Stimulus Generation ← uses 90% 1e
IPC is used in distributed stimulus generator architectures for transaction exchange.

CITATIONS

4 sources
4 citations — click to collapse
[1] IPC-based transaction exchange [PDF] Crafting a Million Instructions/Sec RISCV-DV - DVCon Proceedings
[2] Asynchronous FIFO functional role [PDF] Crafting a Million Instructions/Sec RISCV-DV - DVCon Proceedings
[3] Shared-memory alternative [PDF] Crafting a Million Instructions/Sec RISCV-DV - DVCon Proceedings
[4] Shared-memory performance contrast [PDF] Crafting a Million Instructions/Sec RISCV-DV - DVCon Proceedings