From: Tavian Barnes <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: RE: [PATCH v4 2/2] io_uring: add support for IORING_OP_GETDENTS
Date: Tue, 16 Mar 2021 11:39:25 -0400 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To:
> IORING_OP_GETDENTS behaves much like getdents64(2) and takes the same
> arguments, but with a small twist: it takes an additional offset
> argument, and reading from the specified directory starts at the given
> offset.
>
> For the first IORING_OP_GETDENTS call on a directory, the offset
> parameter can be set to zero, and for subsequent calls, it can be
> set to the ->d_off field of the last struct linux_dirent64 returned
> by the previous IORING_OP_GETDENTS call.
>
> Internally, if necessary, IORING_OP_GETDENTS will vfs_llseek() to
> the right directory position before calling vfs_getdents().
For my envisioned use case it would be important to support reading from
the current file position when offset == -1 (IORING_FEAT_RW_CUR_POS).
Among other things, this would let me fully read a directory with fewer
round-trips. Normally after the first getdents(), another one must be
issued to distinguish between EOF and a short first read. It would be
nice to do both calls with linked SQEs so I could immediately know that
I've reached the end of the directory.
> IORING_OP_GETDENTS may or may not update the specified directory's
> file offset, and the file offset should not be relied upon having
> any particular value during or after an IORING_OP_GETDENTS call.
Obviously for the above to work, we'd have to get rid of this
limitation. Is that possible?
next reply other threads:[~2021-03-16 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 15:39 Tavian Barnes [this message]
2021-03-16 16:11 ` [PATCH v4 2/2] io_uring: add support for IORING_OP_GETDENTS Lennert Buytenhek
-- strict thread matches above, loose matches on Subject: below --
2021-03-12 15:48 [PATCH v4 0/2] " Lennert Buytenhek
2021-03-12 15:50 ` [PATCH v4 2/2] " Lennert Buytenhek
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=ea2b3ae7-d5c4-a46e-1d2d-e2c7b5fd8730@tavianator.com \
[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