From dee00d0de3528ab5a21adec00fa125f8735f1bb1 Mon Sep 17 00:00:00 2001 From: lty Date: Tue, 9 Dec 2025 17:52:24 +0800 Subject: [PATCH] [Usability]local_buffer_size support for units: GB, MB, KB, B (#4829) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit What this PR does / why we need it? Improve usability，local_buffer_size support for units: GB, MB, KB, B, For example, "2GB" { "local_hostname": "XXX.XXX.XXX.XXX", "metadata_server": "P2PHANDSHAKE", "protocol": "ascend", "device_name": "", "use_ascend_direct": true, "master_server_address": "XXX.XXX.XXX.XXX:50088", "global_segment_size": 60000000000, "local_buffer_size": "2GB" } Does this PR introduce any user-facing change? local_buffer_size support for units: GB, MB, KB, B How was this patch tested? Mooncake configures local_buffer_size as GB, MB, KB, B - vLLM version: v0.12.0 - vLLM main: https://github.com/vllm-project/vllm/commit/ad32e3e19ccf0526cb6744a5fed09a138a5fb2f9 Signed-off-by: lty --- vllm_ascend/distributed/kvpool/backend/mooncake_backend.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/vllm_ascend/distributed/kvpool/backend/mooncake_backend.py b/vllm_ascend/distributed/kvpool/backend/mooncake_backend.py index 6fb0d259..5a9f2a4b 100644 --- a/vllm_ascend/distributed/kvpool/backend/mooncake_backend.py +++ b/vllm_ascend/distributed/kvpool/backend/mooncake_backend.py @@ -94,8 +94,8 @@ class MooncakeStoreConfig: global_segment_size=_parse_global_segment_size( config.get("global_segment_size", DEFAULT_GLOBAL_SEGMENT_SIZE)), - local_buffer_size=(config.get("local_buffer_size", - DEFAULT_LOCAL_BUFFER_SIZE)), + local_buffer_size=_parse_global_segment_size( + config.get("local_buffer_size", DEFAULT_LOCAL_BUFFER_SIZE)), protocol=config.get("protocol", "tcp"), device_name=config.get("device_name", ""), master_server_address=config.get("master_server_address"))