-
Notifications
You must be signed in to change notification settings - Fork 0
Issues: JackKelly/light-speed-io
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Benchmark New feature or request
performance
Improvements to runtime performance
testing_benchmarking_CI
Automatically ensuring the code behaves
lsio_uring
enhancement
Stop using iterations (in GitHub). Instead use milestones.
documentation
Improvements or additions to documentation
#133
by JackKelly
was closed May 21, 2024
Test new io_uring code
enhancement
New feature or request
testing_benchmarking_CI
Automatically ensuring the code behaves
#128
by JackKelly
was closed May 17, 2024
Implement the simplest io_uring "worker" using threads &
crossbeam::deque
#122
by JackKelly
was closed May 15, 2024
Typestate
: Use a custom type for each state (for each IoOperation
) & use Rust's type system to make sure we only progress forwards
enhancement
#117
by JackKelly
was closed Mar 29, 2024
Create a New feature or request
struct UserData
to manage how we encode uring user_data
enhancement
#116
by JackKelly
was closed Apr 28, 2024
AlignedBuffer
should use valid_slice
to define the start
and len
that the user is interested in
enhancement
#115
by JackKelly
was closed Apr 22, 2024
Allow New feature or request
AlignedBuffer
to return "owned slices" (like Bytes
), which refer to the same buffer in RAM
enhancement
#114
by JackKelly
was closed Apr 26, 2024
Maybe use New feature or request
Bytes
within AlignedBuffer
enhancement
#112
by JackKelly
was closed Mar 26, 2024
New crate: Provide iterator-like methods on a crossbeam channel
enhancement
New feature or request
#106
by JackKelly
was closed Mar 15, 2024
look into using Rayon for the IO thread pool. Can we associate an Improvements to runtime performance
question
Further information is requested
IoUring
instance with each thread? Can we publish tasks to other threads?
performance
#103
by JackKelly
was closed Mar 15, 2024
New crate: New feature or request
performance
Improvements to runtime performance
lsio_optimise_io_plan
(e.g. merge nearby operations; split large ops)
enhancement
#102
by JackKelly
was closed Mar 22, 2024
Ensure that the New feature or request
usability
Make things more user-friendly
read
operation reads the correct number of bytes
enhancement
#97
by JackKelly
was closed Mar 12, 2024
1 task
Why's the io_uring code so slow?! 🙂
performance
Improvements to runtime performance
#95
by JackKelly
was closed Mar 12, 2024
3 of 4 tasks
Use a flat crate structure so this git repo can store multiple (interconnected) crates in a single workspace
enhancement
New feature or request
usability
Make things more user-friendly
#94
by JackKelly
was closed Apr 26, 2024
Drop
ObjectStore
& async
/await
. Use Channels instead. Focus entirely (for now) on io_uring for local file storage.
#93
by JackKelly
was closed Apr 3, 2024
3 of 7 tasks
Reduce code duplication between New feature or request
get
and get_range
enhancement
#90
by JackKelly
was closed Mar 12, 2024
Change New feature or request
Operation
to a Trait
, & use a struct for each operation (get
, get_range
, etc.). Store Trait objects in user_tasks_in_flight
.
enhancement
#86
by JackKelly
was closed Feb 27, 2024
3 tasks done
Convert io_uring opcodes to human-readable op names in errors
#81
by JackKelly
was closed Feb 23, 2024
Don't restrict New feature or request
OperationWithChannel
to always using Vec<u8>
enhancement
#80
by JackKelly
was closed Feb 23, 2024
Implement New feature or request
IoUringLocal::get_range()
(to load one small chunk)
enhancement
#74
by JackKelly
was closed Feb 27, 2024
4 tasks done
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.