[GH-ISSUE #86] [Potential Performance Improvement]fuse_reply can be invoked on different thread than that of request receive #47

New issue

Open

opened 2026-10-26 09:44:08 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-26 09:44:08 +00:00

Owner

Originally created by @z47z on GitHub (Mar 4, 2025).
Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/86

All the fuse request will blocking fuse thread(folly::Coro::blockingWaiting) for now.
But we can invoke fuse_reply_* on any other thread. Blocking is not necessary.

Originally created by @z47z on GitHub (Mar 4, 2025). Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/86 All the fuse request will blocking fuse thread(folly::Coro::blockingWaiting) for now. But we can invoke fuse_reply_* on any other thread. Blocking is not necessary.

bsakaguchi commented

2026-10-26 09:44:09 +00:00

Author

Owner

@huww98 commented on GitHub (Mar 5, 2025):

before we remove blockingWaiting, we can just increase the number of thread.

@huww98 commented on GitHub (Mar 5, 2025): related: https://github.com/deepseek-ai/3FS/pull/83 before we remove blockingWaiting, we can just increase the number of thread.

bsakaguchi referenced this issue

2026-10-26 09:48:06 +00:00

[PR #47] [MERGED] replace magic number 10 with sizeof(kv::Versionstamp) #268