forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 6
Redfs ubuntu noble 6.8.0 58.60 updates reduce queues #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
bsbernd
wants to merge
5
commits into
redfs-ubuntu-noble-6.8.0-58.60
Choose a base branch
from
redfs-ubuntu-noble-6.8.0-58.60-updates-reduce-queues
base: redfs-ubuntu-noble-6.8.0-58.60
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Redfs ubuntu noble 6.8.0 58.60 updates reduce queues #6
bsbernd
wants to merge
5
commits into
redfs-ubuntu-noble-6.8.0-58.60
from
redfs-ubuntu-noble-6.8.0-58.60-updates-reduce-queues
Conversation
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
This is another preparation and will be used for decision which queue to add a request to.
This is preparation for follow up commits that allow to run with a reduced number of queues. Signed-off-by: Bernd Schubert <[email protected]>
jianhuangli
reviewed
Jun 26, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Then tries the first available queue on the
current numa node
other numa nodes?
hbirth
approved these changes
Jun 26, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
So far queue selection was statically - the a request on core X was always handled by the queue corresponding to core X. A previous commit introduced bitmaps that track which queues are available - queue selection can make use of these bitmaps and try to use the ideal queue. Rules are - Tries the queue of the current core first, if available and if that queue does not have too many entries queued - Then tries the first available queue on the current numa node. It does not use random distribution here, because light queue usage is probably ok, so that kernel/userspace switches can be avoided - Then tries the first available global queue ignoring numa nodes. If no queue is free, it tries again the queue of the current core, but if that queue does not exist it falls back to a random queue on the current numa node - that also might not exist - it then uses a random available queue.
Now that queue selection for fuse requests supports missing queues we don't need to wait for full queue initialization. In fact, fuse-server (daemon) might want to run with a reduced number of queues, for example to reduce memory usage. This also simplifies startup - after first queue entry registration fuse-io-uring is ready to be used. Signed-off-by: Bernd Schubert <[email protected]>
2801d80
to
d763efd
Compare
@jianhuangli thank you, updated the commit message. |
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.
No description provided.