Loading...
Searching...
No Matches
RdmaRingDepth.hpp File Reference
Shared BAR1-aware slot-count policy for the RDMA rings. More...
Detailed Description
Shared BAR1-aware slot-count policy for the RDMA rings.
Every pinned RDMA bounce/slot occupies the GPU's PCIe BAR1 aperture (256 MiB on most Quadros) for the card's P2P access. At large rasters (UHD2/8K ~ 32-66 MB frames) a full-depth ring on both the capture and the output side would starve the aperture, so the depth is reduced above a byte threshold. Shared by the GL and Vulkan capture and output RDMA shims so all four agree on the same policy.
Go to the source code of this file.
Classes | |
| struct | score::gfx::interop::RdmaRingDepths |
Namespaces | |
| namespace | score |
| Base toolkit upon which the software is built. | |
| namespace | score::gfx |
| Graphics rendering pipeline for ossia score. | |
Functions | |
| int | score::gfx::interop::rdmaRingDepthForFrame (std::uint32_t frameByteSize, RdmaRingDepths d) noexcept |
Function Documentation
◆ rdmaRingDepthForFrame()
|
inlinenoexcept |
Frames >= 32 MiB use the reduced (large) depth so the pinned slots still fit the BAR1 aperture; smaller frames use the full depth.