Copilot bc17c9b60a Fix P2PHANDSHAKE in dual-NIC container setups via MC_RDMA_BIND_ADDRESS (#2280) ... * Initial plan * Add MC_RDMA_BIND_ADDRESS support for dual-NIC P2PHANDSHAKE setups In dual-NIC environments where TCP and RDMA use separate interfaces, P2PHANDSHAKE mode previously required using a single IP for both TCP handshake and RDMA NIC paths, causing conflicts. This change adds MC_RDMA_BIND_ADDRESS env var support: - When set, RDMA NIC paths use the RDMA-reachable IP - TCP P2P routing continues using the local_server_name IP - Segment descriptors carry rdma_server_name for consistent NIC path construction on both sides - P2P metadata exchange caches RDMA->TCP address mapping so subsequent handshakes resolve to TCP-routable addresses * Changes before error encountered Agent-Logs-Url: https://github.com/kvcache-ai/Mooncake/sessions/fc2826eb-a0ae-450f-b1f4-4ab94269d97a * Apply dual-NIC (MC_RDMA_BIND_ADDRESS) support to TENT transport and update Chinese docs --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>		2026-06-01 16:49:58 +08:00
..
ep-backend.md	Split Mooncake PG out of Mooncake EP (#1387)	2026-01-16 13:39:37 +08:00
mooncake-store.md	[Store] Add opt-in grouped object routing semantics (#2180)	2026-05-27 13:15:57 +08:00
transfer-engine.md	Fix P2PHANDSHAKE in dual-NIC container setups via MC_RDMA_BIND_ADDRESS (#2280)	2026-06-01 16:49:58 +08:00