From: Jens Axboe <axboe@fb.com>
To: "Paolo Valente" <paolo.valente@unimore.it>,
"Matias Bjørling" <m@bjorling.me>,
"Arianna Avanzini" <avanzini@google.com>
Cc: Akinobu Mita <akinobu.mita@gmail.com>,
"Luis R. Rodriguez" <mcgrof@suse.com>,
Ming Lei <ming.lei@canonical.com>,
Mike Krinkin <krinkin.m.u@gmail.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH BUGFIX V2 0/3] null_blk: fix throughput losses and hangs
Date: Tue, 1 Dec 2015 10:52:32 -0700 [thread overview]
Message-ID: <565DDE60.3000800@fb.com> (raw)
In-Reply-To: <1448966899-3399-1-git-send-email-paolo.valente@unimore.it>
On 12/01/2015 03:48 AM, Paolo Valente wrote:
> Hi,
> here is an updated version of the patchset, differing from the
> previous version only in that it reinstates the missing extra check
> pointed out in [2]. For your convenience, the content of the cover
> letter for the previous version follows.
>
> While doing some tests with the null_blk device driver, we bumped into
> two problems: first, unjustified and in some cases high throughput
> losses; second, actual hangs. These problems seem to be the
> consequence of the combination of three causes, and this patchset
> introduces a fix for each of these causes. In particular, changes
> address:
> . an apparent flaw in the logic with which delayed completions are
> implemented: this flaw causes, with unlucky but non-pathological
> workloads, actual request-completion delays to become arbitrarily
> larger than the configured delay;
> . the missing restart of the device queue on the completion of a request in
> single-queue non-delayed mode;
> . the overflow of the request-delay parameter, when extremely high values
> are used (e.g., to spot bugs).
>
> To avoid possible confusion, we stress that these fixes *do not* have
> anything to do with the problems highlighted in [1] (tests of the
> multiqueue xen-blkfront and xen-blkback modules with null_blk).
>
> You can find more details in the patch descriptions.
Thanks Paolo, added.
--
Jens Axboe
next prev parent reply other threads:[~2015-12-01 17:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 14:31 [PATCH BUGFIX 0/3] null_blk: fix throughout losses and hangs Paolo Valente
2015-11-02 14:31 ` [PATCH BUGFIX 1/3] null_blk: set a separate timer for each command Paolo Valente
2015-11-02 16:14 ` Jens Axboe
2015-11-03 9:01 ` Paolo Valente
2015-11-29 17:27 ` Paolo Valente
2015-11-30 15:55 ` Jens Axboe
2015-12-01 10:48 ` [PATCH BUGFIX V2 0/3] null_blk: fix throughput losses and hangs Paolo Valente
2015-12-01 10:48 ` [PATCH BUGFIX V2 1/3] null_blk: set a separate timer for each command Paolo Valente
2015-12-01 10:48 ` [PATCH BUGFIX V2 2/3] null_blk: guarantee device restart in all irq modes Paolo Valente
2015-12-01 10:48 ` [PATCH BUGFIX V2 3/3] null_blk: change type of completion_nsec to unsigned long Paolo Valente
2015-12-01 17:52 ` Jens Axboe [this message]
2015-11-02 14:31 ` [PATCH BUGFIX 2/3] null_blk: guarantee device restart in all irq modes Paolo Valente
2015-11-02 16:25 ` Jens Axboe
2015-11-03 9:02 ` Paolo Valente
2015-11-02 14:31 ` [PATCH BUGFIX 3/3] null_blk: change type of completion_nsec to unsigned long Paolo Valente
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=565DDE60.3000800@fb.com \
--to=axboe@fb.com \
--cc=akinobu.mita@gmail.com \
--cc=avanzini@google.com \
--cc=krinkin.m.u@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m@bjorling.me \
--cc=mcgrof@suse.com \
--cc=ming.lei@canonical.com \
--cc=paolo.valente@unimore.it \
/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;
as well as URLs for NNTP newsgroup(s).