tursodatabase / tursodatabase/libsql
Provide io_uring-based VFS implementation
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Requires https://github.com/libsql/libsql/issues/3. Once the interface is ready for asynchronous I/O, the next natural step is to provide a VFS implementation based on io_uring, probably in poll mode to be in line with the existing sqlite3 semantics of returning SQLITE_BUSY if the statement is not ready to proceed just yet.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked libsql issue #3 to understand the required asynchronous I/O interface, then review SQLite VFS semantics and io_uring poll mode. Done means providing the VFS implementation so operations that are not ready return SQLITE_BUSY consistently with the stated behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- databases, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100