From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
io-uring Mailing List <io-uring@vger.kernel.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christian Mazakas <christian.mazakas@gmail.com>,
Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
Subject: [PATCH liburing] liburing.h: Only use `IOURINGINLINE` macro for FFI functions
Date: Tue, 1 Jul 2025 03:36:40 +0700 [thread overview]
Message-ID: <20250630203641.1217131-1-ammarfaizi2@gnuweeb.org> (raw)
From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
These 3 inline functions are for liburing internal use, it does not
make much sense to export them:
uring_ptr_to_u64
io_uring_cqe_iter_init
io_uring_cqe_iter_next
Don't use IOURINGINLINE on them. Also, add a comment on the
IOURINGINLINE macro definition explaining when to use IOURINGINLINE
and remind the reader to add the exported function to liburing-ffi.map
if they introduce a function marked with IOURINGINLINE.
Cc: Christian Mazakas <christian.mazakas@gmail.com>
Cc: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
---
src/include/liburing.h | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/src/include/liburing.h b/src/include/liburing.h
index 35d2b271b546..3948a5a6ed47 100644
--- a/src/include/liburing.h
+++ b/src/include/liburing.h
@@ -28,6 +28,13 @@
#define uring_likely(cond) __builtin_expect(!!(cond), 1)
#endif
+/*
+ * NOTE: Only use IOURINGINLINE macro for 'static inline' functions
+ * that are expected to be available in the FFI bindings.
+ *
+ * Functions that are marked as IOURINGINLINE should be
+ * included in the liburing-ffi.map file.
+ */
#ifndef IOURINGINLINE
#define IOURINGINLINE static inline
#endif
@@ -146,7 +153,7 @@ struct io_uring_zcrx_rq {
* Library interface
*/
-IOURINGINLINE __u64 uring_ptr_to_u64(const void *ptr)
+static inline __u64 uring_ptr_to_u64(const void *ptr)
{
return (__u64) (unsigned long) ptr;
}
@@ -360,7 +367,7 @@ struct io_uring_cqe_iter {
unsigned tail;
};
-IOURINGINLINE struct io_uring_cqe_iter
+static inline struct io_uring_cqe_iter
io_uring_cqe_iter_init(const struct io_uring *ring)
{
return (struct io_uring_cqe_iter) {
@@ -373,7 +380,7 @@ io_uring_cqe_iter_init(const struct io_uring *ring)
};
}
-IOURINGINLINE bool io_uring_cqe_iter_next(struct io_uring_cqe_iter *iter,
+static inline bool io_uring_cqe_iter_next(struct io_uring_cqe_iter *iter,
struct io_uring_cqe **cqe)
{
if (iter->head == iter->tail)
--
Ammar Faizi
next reply other threads:[~2025-06-30 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 20:36 Ammar Faizi [this message]
2025-06-30 20:41 ` [PATCH liburing] liburing.h: Only use `IOURINGINLINE` macro for FFI functions Alviro Iskandar Setiawan
2025-06-30 21:39 ` 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=20250630203641.1217131-1-ammarfaizi2@gnuweeb.org \
--to=ammarfaizi2@gnuweeb.org \
--cc=alviro.iskandar@gnuweeb.org \
--cc=axboe@kernel.dk \
--cc=christian.mazakas@gmail.com \
--cc=gwml@vger.gnuweeb.org \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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