All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"kys@microsoft.com" <kys@microsoft.com>,
	"longli@microsoft.com" <longli@microsoft.com>,
	"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "sthemmin@microsoft.com" <sthemmin@microsoft.com>
Subject: Re: [PATCH] block-mq: set both block queue and hardware queue restart bit for restart
Date: Fri, 5 May 2017 19:52:12 +0000	[thread overview]
Message-ID: <1494013930.2744.16.camel@sandisk.com> (raw)
In-Reply-To: <BN3PR03MB2227328E61F98787E89B36B5CEEB0@BN3PR03MB2227.namprd03.prod.outlook.com>

On Fri, 2017-05-05 at 08:58 +0000, Long Li wrote:
> > > From: Bart Van Assche [mailto:Bart.VanAssche@sandisk.com]
> > >=20
> > > Can you repeat your test with kernel v4.11-rc6?
> > > The patches that went into the block layer for v4.11-rc6 should be
> > > sufficient to fix this: [ ... ]
>=20
> Testing went well. There were no I/O hangs.

Hello Long,

Thanks for having run these tests and thanks for the feedback!

Bart.=

WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"kys@microsoft.com" <kys@microsoft.com>,
	"longli@microsoft.com" <longli@microsoft.com>,
	"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "sthemmin@microsoft.com" <sthemmin@microsoft.com>
Subject: Re: [PATCH] block-mq: set both block queue and hardware queue restart bit for restart
Date: Fri, 5 May 2017 19:52:12 +0000	[thread overview]
Message-ID: <1494013930.2744.16.camel@sandisk.com> (raw)
In-Reply-To: <BN3PR03MB2227328E61F98787E89B36B5CEEB0@BN3PR03MB2227.namprd03.prod.outlook.com>

On Fri, 2017-05-05 at 08:58 +0000, Long Li wrote:
> > > From: Bart Van Assche [mailto:Bart.VanAssche@sandisk.com]
> > > 
> > > Can you repeat your test with kernel v4.11-rc6?
> > > The patches that went into the block layer for v4.11-rc6 should be
> > > sufficient to fix this: [ ... ]
> 
> Testing went well. There were no I/O hangs.

Hello Long,

Thanks for having run these tests and thanks for the feedback!

Bart.

  reply	other threads:[~2017-05-05 19:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  0:16 [PATCH] block-mq: set both block queue and hardware queue restart bit for restart Long Li
2017-04-06  0:32 ` Bart Van Assche
2017-04-06  0:32   ` Bart Van Assche
2017-04-06  3:38   ` Long Li
2017-04-06  3:38     ` Long Li
2017-04-06  3:45     ` Bart Van Assche
2017-04-06  3:45       ` Bart Van Assche
2017-04-06  4:21       ` KY Srinivasan
2017-04-06  4:21         ` KY Srinivasan
2017-04-06  5:38         ` Long Li
2017-04-06  5:38           ` Long Li
2017-04-10 23:47         ` Bart Van Assche
2017-04-10 23:47           ` Bart Van Assche
2017-04-13 23:12           ` Long Li
2017-04-13 23:12             ` Long Li
2017-05-05  8:58             ` Long Li
2017-05-05  8:58               ` Long Li
2017-05-05 19:52               ` Bart Van Assche [this message]
2017-05-05 19:52                 ` Bart Van Assche

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=1494013930.2744.16.camel@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=axboe@kernel.dk \
    --cc=kys@microsoft.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longli@microsoft.com \
    --cc=sthemmin@microsoft.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.