-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
WIP: route discards via the I/O queue #2386
Draft
pwrobelse
wants to merge
8
commits into
scylladb:master
Choose a base branch
from
pwrobelse:implement_discard_request_attempt_2
base: master
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.
Draft
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
0f36eee
internal::io_request: add discard operation
pwrobelse 90176fe
io_queue: rename io_desc_read_write to queued_io_request_completion
pwrobelse dc3f119
reactor: expose punch_hole() function
pwrobelse eddeffb
io-properties: introduce discard_to_write_ratio
pwrobelse 3916565
io_direction_and_length: introduce 'discard' direction
pwrobelse a64e819
io_queue: allow submission of discard requests
pwrobelse e37e07d
file.cc: submit discards via the I/O queue
pwrobelse 342f088
util/file.hh: implement remove_file_via_blocks_discarding()
pwrobelse 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 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 file contains 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 file contains 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 file contains 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 file contains 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.
I think that discard request should carry write_idx direction and whether or not to submit it via sink or via punch_hole() should be decided based on request::op()
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.
Sure, I can revert the change and use
io_direction_and_length::write
for discards. The new direction does not look right in the case ofduplex
mode -- I would not expect three directions in duplex mode.However, if there is no
discard
direction, I see the following three issues that are described below.Firstly, if the write direction is used, then the calculation in
internal::request_tokens()
will need to contain a new if statement. It is going to distinguish between true write requests and discard requests (based on operation type), because the coefficients are different for write/discard operations.Secondly, I am not sure about the usage of
_group->_max_request_length[]
. If I understand correctly, the maximum request length is different for discards and for writes. So, simple usage of_group->_max_request_length[direction]
will be invalid. Somehow, I feel that it would end up with creation of a new private function that would look similar to the function below:Lastly, the way how statistics are accumulated in
io_queue::priority_class_data::on_dispatch()
will mix discards and writes. The code looks as follows:_rwstat[dnl.rwd_idx()].add(dnl.length());
.If the three mentioned points do not cause a problem, then I will introduce the change.