From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Subject: Re: [PATCH v2 0/2] implement timeout update
Date: Mon, 30 Nov 2020 15:53:58 -0700 [thread overview]
Message-ID: <040eb01f-37cf-3db1-9090-0ce99d65527c@kernel.dk> (raw)
In-Reply-To: <cover.1606763415.git.asml.silence@gmail.com>
On 11/30/20 12:11 PM, Pavel Begunkov wrote:
> Timeout update is a IORING_OP_TIMEOUT_REMOVE request with timeout_flags
> containing a new IORING_TIMEOUT_UPDATE flag. Even though naming may be
> confusing, but update and remove are very similar both code and
> functionality wise, so doesn't seem necessary to add a new opcode.
>
> Updates don't support offsets, but I don't see a need either. Can
> be implemented in the future by passing it in sqe->len.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-11-30 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 19:11 [PATCH v2 0/2] implement timeout update Pavel Begunkov
2020-11-30 19:11 ` [PATCH v2 1/2] io_uring: restructure io_timeout_cancel() Pavel Begunkov
2020-11-30 19:11 ` [PATCH v2 2/2] io_uring: add timeout update Pavel Begunkov
2020-11-30 22:53 ` 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=040eb01f-37cf-3db1-9090-0ce99d65527c@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
/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