From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [PATCH liburing 8/8] Remove leftovers of old reg-wait registration api
Date: Fri, 15 Nov 2024 21:33:55 +0000 [thread overview]
Message-ID: <3c0b35b519e0ee52c4fe8ed5aa1c2498a55470e9.1731705935.git.asml.silence@gmail.com> (raw)
In-Reply-To: <[email protected]>
Signed-off-by: Pavel Begunkov <[email protected]>
---
src/include/liburing.h | 3 ---
src/liburing-ffi.map | 2 --
src/liburing.map | 2 --
src/setup.c | 10 ----------
4 files changed, 17 deletions(-)
diff --git a/src/include/liburing.h b/src/include/liburing.h
index 81ffe6e..627fc47 100644
--- a/src/include/liburing.h
+++ b/src/include/liburing.h
@@ -289,9 +289,6 @@ int io_uring_register(unsigned int fd, unsigned int opcode, const void *arg,
*/
int io_uring_register_region(struct io_uring *ring,
struct io_uring_mem_region_reg *reg);
-struct io_uring_reg_wait *io_uring_setup_reg_wait(struct io_uring *ring,
- unsigned nentries, int *err);
-void io_uring_free_reg_wait(struct io_uring_reg_wait *reg, unsigned nentries);
/*
* Mapped buffer ring alloc/register + unregister/free helpers
diff --git a/src/liburing-ffi.map b/src/liburing-ffi.map
index 117a46a..9af1fb9 100644
--- a/src/liburing-ffi.map
+++ b/src/liburing-ffi.map
@@ -221,8 +221,6 @@ LIBURING_2.9 {
io_uring_resize_rings;
io_uring_register_wait_reg;
io_uring_submit_and_wait_reg;
- io_uring_free_reg_wait;
- io_uring_setup_reg_wait;
io_uring_clone_buffers_offset;
io_uring_register_region;
} LIBURING_2.8;
diff --git a/src/liburing.map b/src/liburing.map
index 46edbc9..9f7b211 100644
--- a/src/liburing.map
+++ b/src/liburing.map
@@ -108,8 +108,6 @@ LIBURING_2.9 {
io_uring_resize_rings;
io_uring_register_wait_reg;
io_uring_submit_and_wait_reg;
- io_uring_free_reg_wait;
- io_uring_setup_reg_wait;
io_uring_clone_buffers_offset;
io_uring_register_region;
} LIBURING_2.8;
diff --git a/src/setup.c b/src/setup.c
index 7c0cfab..d4694f5 100644
--- a/src/setup.c
+++ b/src/setup.c
@@ -686,13 +686,3 @@ int io_uring_free_buf_ring(struct io_uring *ring, struct io_uring_buf_ring *br,
__sys_munmap(br, nentries * sizeof(struct io_uring_buf));
return 0;
}
-
-void io_uring_free_reg_wait(struct io_uring_reg_wait *reg, unsigned nentries)
-{
-}
-
-struct io_uring_reg_wait *io_uring_setup_reg_wait(struct io_uring *ring,
- unsigned nentries, int *err)
-{
- return NULL;
-}
--
2.46.0
next prev parent reply other threads:[~2024-11-15 21:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 21:33 [PATCH liburing 0/8] update reg-wait to use region API Pavel Begunkov
2024-11-15 21:33 ` [PATCH liburing 1/8] queue: break reg wait setup Pavel Begunkov
2024-11-15 21:33 ` [PATCH liburing 2/8] Update io_uring.h Pavel Begunkov
2024-11-15 21:33 ` [PATCH liburing 3/8] queue: add region helpers and fix up wait reg kernel api Pavel Begunkov
2024-11-15 21:33 ` [PATCH liburing 4/8] examples: convert reg-wait to new api Pavel Begunkov
2024-11-15 21:33 ` [PATCH liburing 5/8] tests: convert reg-wait to regions Pavel Begunkov
2024-11-15 21:33 ` [PATCH liburing 6/8] tests: add region testing Pavel Begunkov
2024-11-15 21:33 ` [PATCH liburing 7/8] tests: test arbitrary offset reg waits Pavel Begunkov
2024-11-15 21:33 ` Pavel Begunkov [this message]
2024-11-16 17:07 ` [PATCH liburing 0/8] update reg-wait to use region API Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3c0b35b519e0ee52c4fe8ed5aa1c2498a55470e9.1731705935.git.asml.silence@gmail.com \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox