forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 9
Fix key performance issues in 6.17 with byte range locks #202
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
hbirth
wants to merge
17
commits into
DDNStorage:redfs-ubuntu-hwe-6.17.0-16.16-24.04.1
Choose a base branch
from
hbirth:redfs-ubuntu-hwe-6.17.0-16.16-24.04.1
base: redfs-ubuntu-hwe-6.17.0-16.16-24.04.1
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.
+2,161
−972
Open
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
7499e44
fuse: refuse a writeback connection whose block is not a page
hbirth 8c2ff0e
fuse: take a DLM read lock for the readahead window
hbirth 6bc7637
fuse: hold DLM grants as a bitmap and drive every path from it
hbirth 7630edf
fuse: carry the write retry flag in iomap's private pointer
hbirth 660b67b
fuse: retry a DLM grant the server refuses as contended
hbirth 6fa095c
fuse: keep a folio writeback could not send
hbirth 07d9e7b
fuse: keep the local size against an attribute reply already on the wire
hbirth a4411a0
fuse: do not ask for a grant from inside the revoke handler
hbirth 73e2ae1
fuse: take the writeback grant with no folio held
hbirth a04d9fb
fuse: do not record a grant past what a revoke could mark
hbirth e7b2183
fuse: say that the readahead grant is taken under the folio locks
hbirth 20e357a
fuse: bound the range a writeback pass defers
hbirth d444eee
fuse: put a skipped folio back on the dirty list after iomap lets go
hbirth dd2e0db
fuse: fix the two writethrough paths a large folio breaks
hbirth a3d93d0
fuse: do not lose a folio writeback declined to send
hbirth 520aed9
fuse: pin a dlm grant from confirmation to dirty
hbirth b901618
fuse: default large folios off
hbirth File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
Why removing the O_APPEND flag here? The redfsd daemon code relies on this flag as well... Removing this flag will break the function in redfsd.
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.
with writeback you don't want to always write 'at the end' ... especially if you have done it a couple of times and you lose a lock in the middle