From: Jens Axboe <[email protected]>
To: Shuveb Hussain <[email protected]>
Cc: [email protected]
Subject: Re: Unclear documentation about IORING_OP_READ
Date: Tue, 1 Sep 2020 08:02:32 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAF=AFaLxuUutwB94JXdRuCf0vWHNUPNeX71Pk8VpHpKML5PntQ@mail.gmail.com>
On 9/1/20 6:51 AM, Shuveb Hussain wrote:
> Hello,
>
>> This is intended behavior, you should consider the READV to be just
>> like preadv2() in that it takes the offset/iov/flags, and ditto on
>> the write side. READ is basically what a pread2 would be, if it
>> existed.
>>
>> That said, you can use off == -1 if IORING_FEAT_RW_CUR_POS is set
>> in the feature flags upon ring creation, and that'll use (and updated)
>> the current file offset. This works for any non-stream/pipe file
>> type.
>>
>
> That clarifies it. Thanks, Jens.
Great! BTW, thanks for working on the io_uring(7) man page, I'm pretty
excited about that.
--
Jens Axboe
prev parent reply other threads:[~2020-09-01 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 3:32 Unclear documentation about IORING_OP_READ Shuveb Hussain
2020-08-30 20:10 ` Jens Axboe
2020-09-01 12:51 ` Shuveb Hussain
2020-09-01 14:02 ` Jens Axboe [this message]
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] \
[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