[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CO2PR03MB2230865504BF560409A0606FCE0D0@CO2PR03MB2230.namprd03.prod.outlook.com>
Date: Thu, 6 Apr 2017 05:38:10 +0000
From: Long Li <longli@...rosoft.com>
To: KY Srinivasan <kys@...rosoft.com>,
Bart Van Assche <Bart.VanAssche@...disk.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"axboe@...nel.dk" <axboe@...nel.dk>
CC: Stephen Hemminger <sthemmin@...rosoft.com>
Subject: RE: [PATCH] block-mq: set both block queue and hardware queue restart
bit for restart
> -----Original Message-----
> From: KY Srinivasan
> Sent: Wednesday, April 5, 2017 9:21 PM
> To: Bart Van Assche <Bart.VanAssche@...disk.com>; linux-
> kernel@...r.kernel.org; linux-block@...r.kernel.org; Long Li
> <longli@...rosoft.com>; axboe@...nel.dk
> Cc: Stephen Hemminger <sthemmin@...rosoft.com>
> Subject: RE: [PATCH] block-mq: set both block queue and hardware queue
> restart bit for restart
>
>
>
> > -----Original Message-----
> > From: Bart Van Assche [mailto:Bart.VanAssche@...disk.com]
> > Sent: Wednesday, April 5, 2017 8:46 PM
> > To: linux-kernel@...r.kernel.org; linux-block@...r.kernel.org; Long Li
> > <longli@...rosoft.com>; axboe@...nel.dk
> > Cc: Stephen Hemminger <sthemmin@...rosoft.com>; KY Srinivasan
> > <kys@...rosoft.com>
> > Subject: Re: [PATCH] block-mq: set both block queue and hardware queue
> > restart bit for restart
> >
> > On Thu, 2017-04-06 at 03:38 +0000, Long Li wrote:
> > > > -----Original Message-----
> > > > From: Bart Van Assche [mailto:Bart.VanAssche@...disk.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.
>
> The tests that indicated the issue were run Hyper-V. The driver is
> storvsc_drv.c The I/O scheduler was I think noop.
Yes, we see I/O hung on scheduler none. Also tried on mq-deadline, same hung with the same cause.
>
> K. Y
> >
> > Thanks,
> >
> > Bart.
Powered by blists - more mailing lists