fix

Author: MalikHou

docs/cn/rdma.md

@@ -50,24 +50,17 @@ RDMA是硬件相关的通信技术，有很多独特的概念，比如device、p
 RDMA支持事件驱动和轮询两种模式，默认是事件驱动模式，通过设置rdma_use_polling可以开启轮询模式。轮询模式下还可以设置轮询器数目（rdma_poller_num），以及是否主动放弃CPU（rdma_poller_yield）。轮询模式下还可以设置一个回调函数，在每次轮询时调用，可以配合io_uring/spdk等使用。
 
 `event_dispatcher_edisp_unsched` 是全局开关，同时影响普通模式（TCP）和 RDMA 模式的 EventDispatcher 调度行为。
-它用于替代 `rdma_edisp_unsched`。当前保留 `rdma_edisp_unsched` 仅用于兼容历史命令行，未来版本会移除。两者语义一致：值为 `true` 时都表示 EventDispatcher 不可被调度。
+值为 `true` 时 EventDispatcher 不可被调度，值为 `false` 时保持可调度（默认）。
 
-历史说明：之前 RDMA 路径里出现过一次 `if` 判断 bug，导致行为和 flag 语义不一致；当前逻辑已修复，并按统一语义生效。
-
-最终生效条件统一为：
-`event_dispatcher_edisp_unsched || rdma_edisp_unsched`
-
-启动时不会再改写用户传入的 flag，运行时严格按用户配置值生效。
+运行时严格按用户配置值生效。
 
 推荐使用方式：
-1. 新部署：只配置 `event_dispatcher_edisp_unsched`。
-2. 存量部署：`rdma_edisp_unsched` 仅作过渡兼容，逐步迁移到 `event_dispatcher_edisp_unsched`。
-3. 避免脚本中给出“冲突值”；在统一 OR 语义下，只要任一 flag 为 `true`，EventDispatcher 就不可调度。
+1. 默认不配置，保持 `false`。
+2. 需要不可调度行为时，设置 `-event_dispatcher_edisp_unsched=true`。
 
 行为示例：
-1. 仅设置 `-rdma_edisp_unsched=true`：`rdma_edisp_unsched=true`、`event_dispatcher_edisp_unsched=false`；TCP和RDMA均不可调度。
-2. 仅设置 `-event_dispatcher_edisp_unsched=true`：`rdma_edisp_unsched=false`、`event_dispatcher_edisp_unsched=true`；TCP和RDMA均不可调度。
-3. 同时设置 `-rdma_edisp_unsched=true -event_dispatcher_edisp_unsched=false`：`rdma_edisp_unsched=true`、`event_dispatcher_edisp_unsched=false`；TCP和RDMA均不可调度。
+1. `-event_dispatcher_edisp_unsched=false`：TCP 和 RDMA 均可调度。
+2. `-event_dispatcher_edisp_unsched=true`：TCP 和 RDMA 均不可调度。
 
 # 参数
 
@@ -94,5 +87,4 @@ RDMA支持事件驱动和轮询两种模式，默认是事件驱动模式，通
 * rdma_poller_num: 轮询模式下的poller数目，默认1。
 * rdma_poller_yield: 轮询模式下的poller是否主动放弃CPU，默认是false。
 * event_dispatcher_edisp_unsched: 全局开关，控制EventDispatcher是否不可被调度（true时不可调度），默认是false。
-* rdma_edisp_unsched: 废弃兼容参数（未来版本计划移除）。当前仍参与统一生效判断，默认是false。
 * rdma_disable_bthread: 禁用bthread，默认是false。

docs/en/rdma.md

@@ -48,24 +48,17 @@ The application can manage memory by itself and send data with IOBuf::append_use
 RDMA is hardware-related. It has some different concepts such as device, port, GID, LID, MaxSge and so on. These parameters can be read from NICs at initialization, and brpc will make the default choice (see src/brpc/rdma/rdma_helper.cpp). Sometimes the default choice is not the expectation, then it can be changed in the flag way.
 
 `event_dispatcher_edisp_unsched` is a global flag and affects EventDispatcher scheduling in both normal mode (TCP) and RDMA mode.
-It replaces `rdma_edisp_unsched`. `rdma_edisp_unsched` is still kept only for command-line compatibility and is planned for removal in a future release. The two flags have the same semantics: `true` means EventDispatcher is unschedulable.
+`true` means EventDispatcher is unschedulable, and `false` means schedulable (default).
 
-Historical note: there was a previous `if`-condition bug on the RDMA path, where behavior did not match the flag semantics. The logic is now fixed and follows the unified semantics.
-
-The effective unsched condition is unified as:
-`event_dispatcher_edisp_unsched || rdma_edisp_unsched`
-
-No startup synchronization rewrites user flags. Runtime behavior is determined directly from user-provided values.
+Runtime behavior is determined directly from user-provided values.
 
 Recommended usage:
-1. New deployment: set only `event_dispatcher_edisp_unsched`.
-2. Existing deployment: keep `rdma_edisp_unsched` temporarily, but migrate to `event_dispatcher_edisp_unsched`.
-3. Avoid conflicting values in scripts; with unified OR semantics, either flag being `true` makes EventDispatcher unschedulable.
+1. Keep the default `false` when unsched is not needed.
+2. Set `-event_dispatcher_edisp_unsched=true` when unsched behavior is required.
 
 Examples:
-1. Only `-rdma_edisp_unsched=true`: `rdma_edisp_unsched=true`, `event_dispatcher_edisp_unsched=false`; both TCP and RDMA are unschedulable.
-2. Only `-event_dispatcher_edisp_unsched=true`: `rdma_edisp_unsched=false`, `event_dispatcher_edisp_unsched=true`; both TCP and RDMA are unschedulable.
-3. Both `-rdma_edisp_unsched=true -event_dispatcher_edisp_unsched=false`: `rdma_edisp_unsched=true`, `event_dispatcher_edisp_unsched=false`; both TCP and RDMA are unschedulable.
+1. `-event_dispatcher_edisp_unsched=false`: both TCP and RDMA are schedulable.
+2. `-event_dispatcher_edisp_unsched=true`: both TCP and RDMA are unschedulable.
 
 # Parameters
 
@@ -92,5 +85,4 @@ Configurable parameters:
 * rdma_poller_num: The number of pollers in polling mode, default is 1.
 * rdma_poller_yield: Whether pollers in polling mode voluntarily relinquish the CPU, default is false.
 * event_dispatcher_edisp_unsched: Global switch for EventDispatcher scheduling (true means unschedulable), default is false.
-* rdma_edisp_unsched: Deprecated compatibility flag (planned removal in a future release). It still participates in unified unsched condition, default is false.
 * rdma_disable_bthread: Disables bthread, default is false.

src/brpc/event_dispatcher.cpp

@@ -33,14 +33,6 @@ DEFINE_int32(event_dispatcher_num, 1, "Number of event dispatcher");
 DEFINE_bool(event_dispatcher_edisp_unsched, false,
             "Disable event dispatcher schedule");
 
-#if BRPC_WITH_RDMA
-namespace rdma {
-DEFINE_bool(rdma_edisp_unsched, false,
-            "Deprecated and will be removed in a future release, "
-            "use event_dispatcher_edisp_unsched instead");
-}  // namespace rdma
-#endif
-
 DEFINE_bool(usercode_in_pthread, false, 
             "Call user's callback in pthreads, use bthreads otherwise");
 DEFINE_bool(usercode_in_coroutine, false,
@@ -52,12 +44,7 @@ static bvar::LatencyRecorder* g_edisp_write_lantency = NULL;
 static pthread_once_t g_edisp_once = PTHREAD_ONCE_INIT;
 
 bool EventDispatcherUnsched() {
-#if BRPC_WITH_RDMA
-    return FLAGS_event_dispatcher_edisp_unsched ||
-           rdma::FLAGS_rdma_edisp_unsched;
-#else
     return FLAGS_event_dispatcher_edisp_unsched;
-#endif
 }
 
 static void StopAndJoinGlobalDispatchers() {