From 4f9909021212ab7fd2bc596b773665371fe176da Mon Sep 17 00:00:00 2001
From: Sy03 <1370724210@qq.com>
Date: Mon, 5 Oct 2026 04:26:59 +0800
Subject: [PATCH] [Doc] Specify the host ring process namespace requirement

Signed-off-by: Sy03 <1370724210@qq.com>
---
 docs/design/feature/stage_host_transport.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/design/feature/stage_host_transport.md b/docs/design/feature/stage_host_transport.md
index cddfa340d..ed76731be 100644
--- a/docs/design/feature/stage_host_transport.md
+++ b/docs/design/feature/stage_host_transport.md
@@ -58,6 +58,8 @@ controlled comparisons or deployments with older receivers. Nonzero capacities
 must be between 4 KiB and 64 MiB. All ring endpoints must support this protocol.
 The launcher supplies a common deployment scope; discovery scans only that
 scope's directory. Receive attempts do not wait for another process's file lock.
+Ring endpoints must share a Linux PID namespace. Deployments that share SHM
+across different PID namespaces must use `host_ring_bytes: 0`.
 
 `health()` exposes `host_ring_puts`, `host_ring_gets` and `host_ring_fallbacks`
 alongside the existing counters. Ring setup failure logs once per edge and uses