gx f10413580d docs: cross-container CUDA IPC requires both --ipc и --pid namespace share ...

Реальный тест на 192.168.88.98 (1920x1080 HEVC, 25fps) показал: для отдельных
consumer-container'ов недостаточно ipc=container:X — нужен также
pid=container:X, иначе cudaIpcOpenEventHandle падает с invalid device
context. CUDA driver валидирует IPC peer через /proc/<pid>/...

E2E на реальной камере проверен:
  publisher (отдельный контейнер) -> consumer (docker exec): 250 frames, 0 gaps
  publisher (отдельный контейнер) -> consumer (отдельный с pid+ipc): 200, 0 gaps

Обновлено:
- docs/integration.md compose snippet, verification, troubleshooting section
- docker-compose.example.yml — добавлен pid: container:cuframes-cam-test
- README.md quickstart — добавлен --pid в docker run subscriber

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-05-15 06:37:09 +01:00

..

measurements

spike-v2: validate sync semantics (R1/R2 architectural review)

2026-05-14 23:00:13 +01:00

architecture.md

arch: close open question §6.6 — events as default for cross-process sync

2026-05-14 23:00:40 +01:00

benchmarks-phase0.md

phase0: benchmark results — PASSED on RTX 5090 (Blackwell sm_120)

2026-05-14 22:02:49 +01:00

integration.md

docs: cross-container CUDA IPC requires both --ipc и --pid namespace share

2026-05-15 06:37:09 +01:00

protocol.md

docs(protocol): bit-exact wire protocol specification (R4)

2026-05-14 23:04:46 +01:00

requirements.md

docs: system requirements (hardware, software, build, Docker, k8s)

2026-05-14 23:11:30 +01:00