Repository navigation
Conversation
Signed-off-by: Schatten <czhengt@qq.com>
bitborne
requested review from
XucSh,
YiXR,
stmatengss and
ykwd
as code owners
September 17, 2026 03:25
9 of 14 tasks
Aionw
approved these changes
Sep 18, 2026
This was referenced Sep 21, 2026
11 of 12 tasks
LujhCoconut
added a commit
to LujhCoconut/Mooncake
that referenced
this pull request
Oct 9, 2026
Resolve conflicts between the NoF/SPDK decoupling and mainline work: - Env-var structuration PRs (kvcache-ai#4166/kvcache-ai#4170/kvcache-ai#4203): keep the neutral NoF naming/refactor while adopting the client-owned config structs (NoFDebugConfig, NoFWorkerPoolConfig, FilereadWorkerPoolConfig); QoS byte-limit vars stay in transfer_task.cpp, matching main (open kvcache-ai#4171). - kvcache-ai#3665 embedded master + P2PHANDSHAKE metadata resolution compose with the added nof_initiator injection in Client::Create. - kvcache-ai#4070 TENT native API layered onto the refactored TransferSubmitter. - kvcache-ai#3717 (ShmHelper/receiver shm SPDK registration) is ported from the deleted SpdkWrapper singleton onto the NVMeoFInitiator interface and the process-global NofPageRegistry: registrations normalize to 2MB pages with per-page refcounts, -EBUSY pages are absorbed as external, and a failed Register owns no registration. ShmHelper's singleton is now deliberately leaked so exit-time cleanup can never touch a torn-down registry/env; the SpdkEnvGuard process pin makes the old construction-ordering hack unnecessary.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Part of #3809. Move
MC_NOF_SUBMIT_CHUNK_BYTESandMC_NOF_INFLIGHT_BYTES_LIMITinto a private, client-ownedNoFQosConfigand the common environment catalog. The first QoS construction still caches both byte limits in the original read order, with defaults of 131072 and 33554432 bytes. Absent/empty inputs remain silent; invalid nonempty inputs fall back independently and keep the original raw-value warnings. Conversion to block counts remains inSpdkNofQosbecause it depends on the current block size. No public API or NoF worker/debug setting changes.The shared typed integer parser is used for nonempty input. It intentionally accepts trailing ASCII whitespace (for example,
"2048 "), which the previousstrtolpath rejected. The focused tests cover defaults, independent parsing and fallback, raw warnings and their order, integer boundaries, and process-first-use caching. Block-count assertions are guarded byUSE_NOFand require an enabled build.This is a separate configuration owner from the simultaneously proposed
NoFWorkerPoolConfigPR. Open #3424 renames the QoS type and #3292 changes related QoS code, but neither moves these variables to an owned config. If either merges first and produces a real conflict or behavior change, integrate against the landed code before merge; a behind count alone does not call for rebase.Module
mooncake-store)mooncake-common)Type of Change
How Has This Been Tested?
Test commands:
cmake --build build --target nof_qos_config_test transfer_task_test --parallel 256 ctest --test-dir build --output-on-failure -R '^nof_qos_config_test$' ./scripts/code_format.sh --check --staged pre-commit run --files mooncake-common/include/environment_variables.h mooncake-store/src/CMakeLists.txt mooncake-store/src/transfer_task.cpp mooncake-store/src/config/nof_qos_config.cpp mooncake-store/src/config/nof_qos_config.h mooncake-store/tests/CMakeLists.txt mooncake-store/tests/nof_qos_config_test.cppTest results:
Checklist
./scripts/code_format.shNo documentation change: there is no public API or format change; the typed-parser whitespace normalization is disclosed above.
AI Assistance Disclosure
Codex assisted with owner analysis, implementation, focused tests, build checks, and self-review. The human submitter must review every changed line and be able to defend the change end to end.