From: Jens Axboe <axboe@kernel.dk>
To: Stefan Roesch <shr@fb.com>,
io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH v2 0/3] io_uring: add getdents64 support
Date: Wed, 15 Dec 2021 14:09:52 -0700 [thread overview]
Message-ID: <49b476cb-0de6-22ff-61b7-87ac300b9567@kernel.dk> (raw)
In-Reply-To: <20211124231700.1158521-1-shr@fb.com>
On 11/24/21 4:16 PM, Stefan Roesch wrote:
> This series adds support for getdents64 in liburing. The intent is to
> provide a more complete I/O interface for io_uring.
>
> Patch 1: fs: add parameter use_fpos to iterate_dir()
> This adds a new parameter to the function iterate_dir() so the
> caller can specify if the position is the file position or the
> position stored in the buffer context.
>
> Patch 2: fs: split off vfs_getdents function from getdents64 system call
> This splits of the iterate_dir part of the syscall in its own
> dedicated function. This allows to call the function directly from
> liburing.
>
> Patch 3: io_uring: add support for getdents64
> Adds the functions to io_uring to support getdents64.
>
> There is also a patch series for the changes to liburing. This includes
> a new test. The patch series is called "liburing: add getdents support."
Al, ping on this one as well, same question on the VFS side.
--
Jens Axboe
next prev parent reply other threads:[~2021-12-15 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 23:16 [PATCH v2 0/3] io_uring: add getdents64 support Stefan Roesch
2021-11-24 23:16 ` [PATCH v2 1/3] fs: add parameter use_fpos to iterate_dir function Stefan Roesch
2021-11-24 23:16 ` [PATCH v2 2/3] fs: split off vfs_getdents function of getdents64 syscall Stefan Roesch
2021-11-24 23:17 ` [PATCH v2 3/3] io_uring: add support for getdents64 Stefan Roesch
2021-11-25 4:42 ` [PATCH v2 0/3] io_uring: add getdents64 support Clay Harris
2021-12-01 6:01 ` Stefan Roesch
2021-12-01 7:11 ` Clay Harris
2021-12-15 21:09 ` Jens Axboe [this message]
2021-12-31 23:27 ` Al Viro
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=49b476cb-0de6-22ff-61b7-87ac300b9567@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=shr@fb.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).