From: Jens Axboe <axboe@kernel.dk>
To: Drew DeVault <sir@cmpwn.com>, io-uring@vger.kernel.org
Cc: Pavel Begunkov <asml.silence@gmail.com>
Subject: Re: [PATCH v2] io_uring_enter(2): clarify OP_READ and OP_WRITE
Date: Thu, 27 May 2021 13:05:53 -0600 [thread overview]
Message-ID: <43af392a-9a01-ecee-25cd-54072e0633b4@kernel.dk> (raw)
In-Reply-To: <20210523164437.22784-1-sir@cmpwn.com>
On 5/23/21 10:44 AM, Drew DeVault wrote:
> These do not advance the internal file offset unless the offset is set
> to -1, making them behave more like pread/pwrite than read/write.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-05-27 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 16:44 [PATCH v2] io_uring_enter(2): clarify OP_READ and OP_WRITE Drew DeVault
2021-05-27 19:05 ` 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 \
--in-reply-to=43af392a-9a01-ecee-25cd-54072e0633b4@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=sir@cmpwn.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.