enricobuehler
85bc5b9a3f
linux/zerocopy/* (CUDA context/buffers + EGL/Vulkan dmabuf import + the isolated import worker) and linux/dmabuf_fence.rs move wholesale into crates/pf-zerocopy, so the coming pf-frame vocabulary crate (FramePayload::Cuda owns a DeviceBuffer) and the pf-encode/pf-capture subsystem crates can reach the GPU plumbing without the host orchestrator in between (plan §W6). Content stays Linux-only; the crate compiles to an empty lib elsewhere, so dependents carry a plain dependency. drm_fourcc deliberately does NOT move: it consumes the frame vocabulary (PixelFormat), which sits ABOVE pf-zerocopy — it lives with capture for now and moves into pf-frame next. cuda's ffi re-export bumps pub(crate)->pub (the raw CUdeviceptr vocabulary is consumed across the crate boundary by the encode backends). A crate::zerocopy shim module keeps every existing path valid until capture/encode themselves move out. Verified: Linux clippy -D warnings (pf-zerocopy --all-targets + host nvenc,vulkan-encode,pyrowave --all-targets) + 17/17 pf-zerocopy tests + 321/321 host tests; Windows clippy nvenc,amf-qsv --all-targets Finished exit 0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
23 lines
1.2 KiB
Rust
23 lines
1.2 KiB
Rust
//! Linux GPU zero-copy plumbing (plan §9), extracted from the host's `linux/zerocopy/` module
|
|
//! tree (plan §W6): the shared CUDA context + device buffers, the EGL/Vulkan dmabuf importers,
|
|
//! the isolated import-worker subprocess (client/proto/worker), the zero-copy policy latches, and
|
|
//! the dmabuf implicit-fence wait. Everything is Linux-only; on other targets this crate compiles
|
|
//! to an empty lib so dependents can carry a plain (non-target-gated) dependency.
|
|
//!
|
|
//! The `PixelFormat → DRM FourCC` mapping (`drm_fourcc`) deliberately does NOT live here — it
|
|
//! consumes the shared frame vocabulary, which sits ABOVE this crate (this crate provides the
|
|
//! `DeviceBuffer` that vocabulary's `FramePayload::Cuda` owns).
|
|
|
|
// Unsafe-proof program: every `unsafe {}` / `unsafe impl` must carry a `// SAFETY:` proof. Each
|
|
// file keeps its own `#![deny(...)]` too; this crate-root deny is the catch-all gate.
|
|
#![deny(clippy::undocumented_unsafe_blocks)]
|
|
|
|
/// Wait for a dmabuf's implicit read-ready fence (`DMA_BUF_IOCTL_EXPORT_SYNC_FILE` + poll).
|
|
#[cfg(target_os = "linux")]
|
|
pub mod dmabuf_fence;
|
|
|
|
#[cfg(target_os = "linux")]
|
|
mod imp;
|
|
#[cfg(target_os = "linux")]
|
|
pub use imp::*;
|