From: Stefan Roesch <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Subject: [PATCH v1 0/4] liburing: add getdents64 support
Date: Tue, 23 Nov 2021 10:07:49 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
This adds the getdents support to liburing.
Patch 1: liburing: update io_uring.h header file
This updates the io_uring header file with the new enum for
the getdents support.
Patch 2: liburing: add prepare function for getdents
Adds the io_uring_prep_getdents() function.
Patch 3: liburing: add test program for getdents
Adds a new test program to test the getdents support. It queries
the current directory and all its subdirectories.
Patch 4: liburing: add new man page
Adds a new man page for the io_uring_prep_getdents call.
Stefan Roesch (4):
liburing: update io_uring.h header file
liburing: add prepare function for getdents64
liburing: Add test program for getdents call
liburing: Add man page for io_uring_prep_getdents call
man/io_uring_prep_getdents.3 | 64 ++++++++
src/include/liburing.h | 6 +
src/include/liburing/io_uring.h | 1 +
test/Makefile | 1 +
test/getdents.c | 258 ++++++++++++++++++++++++++++++++
5 files changed, 330 insertions(+)
create mode 100644 man/io_uring_prep_getdents.3
create mode 100644 test/getdents.c
Signed-off-by: Stefan Roesch <[email protected]>
--
2.30.2
next reply other threads:[~2021-11-23 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 18:07 Stefan Roesch [this message]
2021-11-23 18:07 ` [PATCH v1 1/4] liburing: update io_uring.h header file Stefan Roesch
2021-11-23 18:07 ` [PATCH v1 2/4] liburing: add prepare function for getdents64 Stefan Roesch
2021-11-23 18:07 ` [PATCH v1 3/4] liburing: Add test program for getdents call Stefan Roesch
2021-11-23 18:07 ` [PATCH v1 4/4] liburing: Add man page for io_uring_prep_getdents call Stefan Roesch
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 \
[email protected] \
[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