cpp/liburing
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
66a7d05bd82b362942c4f540754b94723c74e804
liburing/src/liburing.h

71 lines
1.5 KiB
C
Raw Normal View History

Initial commit Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 06:51:07 -07:00
#ifndef LIB_URING_H
#define LIB_URING_H
#include <sys/uio.h>
#include "io_uring.h"
/*
* Library interface to io_uring
*/
struct io_uring_sq {
unsigned *khead;
unsigned *ktail;
unsigned *kring_mask;
unsigned *kring_entries;
unsigned *kflags;
unsigned *kdropped;
unsigned *array;
struct io_uring_iocb *iocbs;
unsigned iocb_head;
unsigned iocb_tail;
size_t ring_sz;
};
struct io_uring_cq {
unsigned *khead;
unsigned *ktail;
unsigned *kring_mask;
unsigned *kring_entries;
unsigned *koverflow;
struct io_uring_event *events;
size_t ring_sz;
};
Change API to provide io_uring struct abstraction This is cleaner than having the app juggle an SQ and CQ ring, just wrap them in struct io_uring and have the API always take that. This means the app doesn't need to worry about the different types of rings, and that we only need to pass in one argument for setup/teardown. Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 15:31:35 -07:00
struct io_uring {
struct io_uring_sq sq;
struct io_uring_cq cq;
liburing: include the ring fd in the io_uring No point in keeping these separate. Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 15:59:09 -07:00
int ring_fd;
Change API to provide io_uring struct abstraction This is cleaner than having the app juggle an SQ and CQ ring, just wrap them in struct io_uring and have the API always take that. This means the app doesn't need to worry about the different types of rings, and that we only need to pass in one argument for setup/teardown. Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 15:31:35 -07:00
};
Initial commit Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 06:51:07 -07:00
/*
* System calls
*/
extern int io_uring_setup(unsigned entries, struct iovec *iovecs,
struct io_uring_params *p);
extern int io_uring_enter(unsigned fd, unsigned to_submit,
unsigned min_complete, unsigned flags);
/*
* Library interface
*/
extern int io_uring_queue_init(unsigned entries, struct io_uring_params *p,
Change API to provide io_uring struct abstraction This is cleaner than having the app juggle an SQ and CQ ring, just wrap them in struct io_uring and have the API always take that. This means the app doesn't need to worry about the different types of rings, and that we only need to pass in one argument for setup/teardown. Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 15:31:35 -07:00
struct iovec *iovecs, struct io_uring *ring);
liburing: include the ring fd in the io_uring No point in keeping these separate. Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 15:59:09 -07:00
extern void io_uring_queue_exit(struct io_uring *ring);
extern int io_uring_get_completion(struct io_uring *ring,
Initial commit Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 06:51:07 -07:00
struct io_uring_event **ev_ptr);
liburing: include the ring fd in the io_uring No point in keeping these separate. Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 15:59:09 -07:00
extern int io_uring_wait_completion(struct io_uring *ring,
Add option for getting a completion without waiting This now exposes two helpers: io_uring_get_completion() Return a completion, if we have one (or more) available in the ring io_uring_wait_completion() Return a completion, waiting for it if necessary Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 15:14:07 -07:00
struct io_uring_event **ev_ptr);
liburing: include the ring fd in the io_uring No point in keeping these separate. Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 15:59:09 -07:00
extern int io_uring_submit(struct io_uring *ring);
Change API to provide io_uring struct abstraction This is cleaner than having the app juggle an SQ and CQ ring, just wrap them in struct io_uring and have the API always take that. This means the app doesn't need to worry about the different types of rings, and that we only need to pass in one argument for setup/teardown. Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 15:31:35 -07:00
extern struct io_uring_iocb *io_uring_get_iocb(struct io_uring *ring);
Initial commit Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 06:51:07 -07:00
liburing: add io_uring_iocb_from_ev() helper Returns the iocb associated with a completion event. Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 15:16:55 -07:00
static inline struct io_uring_iocb *
Change API to provide io_uring struct abstraction This is cleaner than having the app juggle an SQ and CQ ring, just wrap them in struct io_uring and have the API always take that. This means the app doesn't need to worry about the different types of rings, and that we only need to pass in one argument for setup/teardown. Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 15:31:35 -07:00
io_uring_iocb_from_ev(struct io_uring *ring, struct io_uring_event *ev)
liburing: add io_uring_iocb_from_ev() helper Returns the iocb associated with a completion event. Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 15:16:55 -07:00
{
Change API to provide io_uring struct abstraction This is cleaner than having the app juggle an SQ and CQ ring, just wrap them in struct io_uring and have the API always take that. This means the app doesn't need to worry about the different types of rings, and that we only need to pass in one argument for setup/teardown. Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 15:31:35 -07:00
return &ring->sq.iocbs[ev->index];
liburing: add io_uring_iocb_from_ev() helper Returns the iocb associated with a completion event. Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 15:16:55 -07:00
}
Initial commit Signed-off-by: Jens Axboe <axboe@kernel.dk>
2019-01-08 06:51:07 -07:00
#endif
Reference in New Issue Copy Permalink