Open
Conversation
I need to figure out the ownership crap.
This range API is powerful, but I completely miseunderstood what double iterator means.
This whole queue thing feels a bit weird, given the position is maintained by the OS... Might need to clone + seek, since we want to maintain this ourselves, since we'll want to eventually use spdk/io_uring.
Keeping the interface so that it is compatible with uring, so not taking buffers by reference, instead owning it. Also pushing pos to each write, which means with current impl I need to open the file everytime.
Need to now open the file every time and I should be able to get what I want.
It doesn't actually control concurrency, but code can use it.
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
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.
TODO
Done
Functions
Commitlog#add
SegmentManager#allocate_when_possible
SegmentManager#active_segment
SegmentManager#current_segment
SegmentManager#new_segment
SegmentManager#finish_and_get_new
SegmentManager#flush_segments
SegmentManager#do_pending_deletes
SegmentManager#acquire_zeroed_buffer
Segment#replenish_reserve
Segment#cycle
Segment#do_flush
Segment#new_buffer
Segment#batch_cycle
Segment#flush
Segment#sync
Segment#reset_sync_time