From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
Pavel Begunkov <asml.silence@gmail.com>,
Breno Leitao <leitao@debian.org>,
Christian Mazakas <christian.mazakas@gmail.com>,
Gilang Fachrezy <gilang4321@gmail.com>,
VNLX Kernel Department <kernel@vnlx.org>,
io-uring Mailing List <io-uring@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>
Subject: [PATCH liburing v1 0/4] liburing updates for 2.4
Date: Thu, 12 Jan 2023 22:57:05 +0700 [thread overview]
Message-ID: <20230112155709.303615-1-ammar.faizi@intel.com> (raw)
From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Hi Jens,
I have found two people confused about the io_uring_prep_splice()
function, especially on the offset part. The current manpage for
io_uring_prep_splice() doesn't tell about the rules of the offset
arguments.
Despite these rules are already noted in "man 2 io_uring_enter",
people who want to know about this prep function will prefer to read
"man 3 io_uring_prep_splice". Let's explain it there.
Additionally, this series also contains:
- Fix a typo: 's/is adjust/is adjusted/' and indentation in
liburing.h.
- Add io_uring_prep_msg_ring_cqe_flags() to liburing-ffi.map.
Commit 27180d7be059 ("Add io_uring_prep_msg_ring_cqe_flags
function") adds a new inline function in liburing.h, but it doesn't
update the liburing-ffi.map file. Update it.
- Note about --nolibc configure option deprecation in the CHANGELOG.
Since commit bfb432f4cce5 ("configure: Always enable `CONFIG_NOLIBC`
if the arch is supported"), the --nolibc configure option is
deprecated and has no effect. Plus, building liburing on x86-64,
x86, and aarch64 always enables CONFIG_NOLIBC. Note these changes
in the CHANGELOG file.
Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
---
Ammar Faizi (4):
liburing-ffi.map: Add io_uring_prep_msg_ring_cqe_flags() function
CHANGELOG: Note about --nolibc configure option deprecation
liburing.h: 's/is adjust/is adjusted/' and fix indentation
man/io_uring_prep_splice.3: Explain more about io_uring_prep_splice()
CHANGELOG | 2 ++
man/io_uring_prep_splice.3 | 38 ++++++++++++++++++++++++++++++++++++++
src/include/liburing.h | 4 ++--
src/liburing-ffi.map | 1 +
4 files changed, 43 insertions(+), 2 deletions(-)
base-commit: 47679a9019e48bf4293a4f55adade9eae715f9e4
--
Ammar Faizi
next reply other threads:[~2023-01-12 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 15:57 Ammar Faizi [this message]
2023-01-12 15:57 ` [PATCH liburing v1 1/4] liburing-ffi.map: Add io_uring_prep_msg_ring_cqe_flags() function Ammar Faizi
2023-01-12 15:57 ` [PATCH liburing v1 2/4] CHANGELOG: Note about --nolibc configure option deprecation Ammar Faizi
2023-01-12 15:57 ` [PATCH liburing v1 3/4] liburing.h: 's/is adjust/is adjusted/' and fix indentation Ammar Faizi
2023-01-12 15:57 ` [PATCH liburing v1 4/4] man/io_uring_prep_splice.3: Explain more about io_uring_prep_splice() Ammar Faizi
2023-01-12 17:26 ` Gabriel Krisman Bertazi
2023-01-12 17:49 ` Jens Axboe
2023-01-12 17:49 ` [PATCH liburing v1 0/4] liburing updates for 2.4 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=20230112155709.303615-1-ammar.faizi@intel.com \
--to=ammarfaizi2@gnuweeb.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=christian.mazakas@gmail.com \
--cc=gilang4321@gmail.com \
--cc=gwml@vger.gnuweeb.org \
--cc=io-uring@vger.kernel.org \
--cc=kernel@vnlx.org \
--cc=leitao@debian.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