mirror of
https://github.com/kvcache-ai/Mooncake.git
synced 2026-11-05 01:17:55 +00:00
[PR #787] [CLOSED] Fixnixlbench #1822
Labels
No labels
ascend
auto-closed
bug
bug
CI/Build
Common
documentation
enhancement
feature request
good first issue
help wanted
high priority
MetaX
nightly-failure
pull-request
PyTorch Backend
question
RFC
Roadmap
stale
Store
Tests
Transfer Engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
kvcache-ai/Mooncake#1822
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/kvcache-ai/Mooncake/pull/787
Author: @haobayuxi
Created: 8/28/2025
Status: ❌ Closed
Base:
main← Head:fixnixlbench📝 Commits (6)
cc2b6c5modify cachelib with slab reallocatedb8e3aa6Merge branch 'kvcache-ai:main' into mainbfff924Merge branch 'kvcache-ai:main' into main60d4cb5Merge branch 'kvcache-ai:main' into mainb658853Merge branch 'kvcache-ai:main' into mainbdf9dd0fix nixl bench bug📊 Changes
7 files changed (+795 additions, -555 deletions)
View changed files
📝
mooncake-store/include/cachelib_memory_allocator/AllocationClass.h(+157 -77)📝
mooncake-store/include/cachelib_memory_allocator/MemoryPool.h(+311 -313)📝
mooncake-store/src/cachelib_memory_allocator/AllocationClass.cpp(+213 -138)📝
mooncake-store/src/cachelib_memory_allocator/MemoryAllocator.cpp(+4 -6)📝
mooncake-store/src/cachelib_memory_allocator/MemoryPool.cpp(+17 -15)📝
mooncake-store/tests/master_service_test.cpp(+91 -2)📝
mooncake-transfer-engine/src/transfer_engine_c.cpp(+2 -4)📄 Description
fix the nixl bench bug. Using strncpy to copy the string without handling the boundary. Occasionally, incorrect characters appear at the end. Causing errors in string matching for nixl. So use strcpy instead. The size of the char[] is malloc as the string size + 1. So using strcpy is fine.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.