mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>,
	io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] timeout fixes
Date: Fri, 1 May 2020 11:21:32 +0300	[thread overview]
Message-ID: <8665e87d-98f8-5973-d11a-03cca3fdf66f@gmail.com> (raw)
In-Reply-To: <cover.1588253029.git.asml.silence@gmail.com>

On 30/04/2020 22:31, Pavel Begunkov wrote:
> [1,2] are small random patches.
> [3,4] are the last 2 timeout patches, but with 1 var renamed.
> [5] fixes a timeout problem related to batched CQ commits. From
> what I see, this should be the last fixing timeouts.

Something gone wrong with testing or rebasing. Never mind this.

> 
> Pavel Begunkov (5):
>   io_uring: check non-sync defer_list carefully
>   io_uring: pass nxt from sync_file_range()
>   io_uring: trigger timeout after any sqe->off CQEs
>   io_uring: don't trigger timeout with another t-out
>   io_uring: fix timeout offset with batch CQ commit
> 
>  fs/io_uring.c | 130 +++++++++++++++++++++-----------------------------
>  1 file changed, 54 insertions(+), 76 deletions(-)
> 

-- 
Pavel Begunkov

  parent reply	other threads:[~2020-05-01  8:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 19:31 Pavel Begunkov
2020-04-30 19:31 ` [PATCH 1/5] io_uring: check non-sync defer_list carefully Pavel Begunkov
2020-04-30 19:31 ` [PATCH 2/5] io_uring: pass nxt from sync_file_range() Pavel Begunkov
2020-04-30 19:31 ` [PATCH 3/5] io_uring: trigger timeout after any sqe->off CQEs Pavel Begunkov
2020-04-30 19:31 ` [PATCH 4/5] io_uring: don't trigger timeout with another t-out Pavel Begunkov
2020-04-30 19:31 ` [PATCH 5/5] io_uring: fix timeout offset with batch CQ commit Pavel Begunkov
2020-05-01  8:21 ` Pavel Begunkov [this message]
2020-05-01  9:38   ` [PATCH 0/5] timeout fixes Pavel Begunkov
2020-05-01  4:26     ` Jens Axboe
2020-05-01 13:55       ` Pavel Begunkov

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=8665e87d-98f8-5973-d11a-03cca3fdf66f@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®