https://nalar.dev/tags/device-drivers/ Recent content in Device Drivers on Nalar Hugo en-us Sat, 19 Sep 2026 00:00:00 +0000 https://nalar.dev/msix-per-vector-masking-separates-interrupt-control-across-device-queues/ Sat, 19 Sep 2026 00:00:00 +0000 https://nalar.dev/msix-per-vector-masking-separates-interrupt-control-across-device-queues/ <h1 id="msi-x-per-vector-masking-separates-interrupt-control-across-device-queues">MSI-X Per-Vector Masking Separates Interrupt Control Across Device Queues</h1> <p>A PCI function using MSI-X can expose multiple interrupt vectors whose delivery state is controlled independently. Software can mask one MSI-X table entry while other enabled entries remain able to signal interrupts. That property matters for devices with multiple queues because interrupt control can follow the same partitioning as the I/O work instead of collapsing every notification source behind one device-wide interrupt state.</p> https://nalar.dev/streaming-dma-mappings-transfer-buffer-ownership-between-cpu-and-device/ Sat, 19 Sep 2026 00:00:00 +0000 https://nalar.dev/streaming-dma-mappings-transfer-buffer-ownership-between-cpu-and-device/ <h1 id="streaming-dma-mappings-transfer-buffer-ownership-between-cpu-and-device">Streaming DMA Mappings Transfer Buffer Ownership Between CPU and Device</h1> <p>A DMA buffer can be valid memory for both a CPU and a device while still requiring a strict handoff between them. Linux streaming DMA mappings express that handoff. The mapping API supplies a device-visible DMA address and gives the DMA layer a point at which architecture-specific cache maintenance, address translation, or bounce buffering can occur.</p> <p>This matters most on systems where device DMA is not automatically coherent with CPU caches, but the ownership rules are part of the portable DMA API even on machines where cache maintenance becomes a no-op.</p>