From: Jens Axboe <[email protected]>
To: Alois Wohlschlager <[email protected]>, [email protected]
Subject: Re: [PATCH] io_uring_enter(2): Clarify how to read from and write to non-seekable files
Date: Tue, 1 Jun 2021 11:10:03 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <2191760.Ec4jsOL7QN@genesis>
On 5/31/21 6:38 AM, Alois Wohlschlager wrote:
> IORING_OP_READ* and IORING_OP_WRITE* all take a file offset. These
> operations can still be used with non-seekable files, as long as the
> offset is set to zero.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-06-01 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 12:38 [PATCH] io_uring_enter(2): Clarify how to read from and write to non-seekable files Alois Wohlschlager
2021-06-01 17:10 ` 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