public inbox for linux-kernel@vger.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>,
	"longli@microsoft.com" <longli@microsoft.com>,
	"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "sthemmin@microsoft.com" <sthemmin@microsoft.com>,
	"kys@microsoft.com" <kys@microsoft.com>
Subject: Re: [PATCH] block-mq: set both block queue and hardware queue restart bit for restart
Date: Thu, 6 Apr 2017 03:45:36 +0000	[thread overview]
Message-ID: <1491450335.8994.1.camel@sandisk.com> (raw)
In-Reply-To: <BN3PR03MB2227E6DBCAE0365A013B7972CE0D0@BN3PR03MB2227.namprd03.prod.outlook.com>

On Thu, 2017-04-06 at 03:38 +0000, Long Li wrote:
> > -----Original Message-----
> > From: Bart Van Assche [mailto:Bart.VanAssche@sandisk.com]
> > 
> > Please drop this patch. I'm working on a better solution.
> 
> Thank you. Looking forward to your patch.

Hello Long,

It would help if you could share the name of the block or SCSI driver with
which you ran into that lockup and also if you could share the name of the
I/O scheduler used in your test.

Thanks,

Bart.

  reply	other threads:[~2017-04-06  3:45 UTC|newest]

Thread overview: 10+ 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  3:38   ` Long Li
2017-04-06  3:45     ` Bart Van Assche [this message]
2017-04-06  4:21       ` KY Srinivasan
2017-04-06  5:38         ` Long Li
2017-04-10 23:47         ` Bart Van Assche
2017-04-13 23:12           ` Long Li
2017-05-05  8:58             ` Long Li
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=1491450335.8994.1.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox