From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH] queue stall with blk-mq-sched To: Jens Axboe References: <762cb508-1de0-93e2-5643-3fe946428eb5@fb.com> <8abc2430-e1fd-bece-ad52-c6d1d482c1e0@suse.de> <1663de5d-cdf7-a6ed-7539-c7d1f5e98f6c@fb.com> <717c595a-a3a6-0508-b537-8cf9e273271e@kernel.dk> Cc: "linux-block@vger.kernel.org" , Omar Sandoval From: Hannes Reinecke Message-ID: <8178340b-dd64-c02d-0ef2-97ad5f928dc8@suse.de> Date: Wed, 25 Jan 2017 08:39:37 +0100 MIME-Version: 1.0 In-Reply-To: <717c595a-a3a6-0508-b537-8cf9e273271e@kernel.dk> Content-Type: text/plain; charset=utf-8 List-ID: On 01/24/2017 11:06 PM, Jens Axboe wrote: > On 01/24/2017 12:55 PM, Jens Axboe wrote: >> Try this patch. We only want to bump it for the driver tags, not the >> scheduler side. > > More complete version, this one actually tested. I think this should fix > your issue, let me know. > Nearly there. The initial stall is gone, but the test got hung at the 'stonewall' sequence again: [global] bs=4k ioengine=libaio iodepth=256 size=4g direct=1 runtime=60 # directory=/mnt numjobs=32 group_reporting cpus_allowed_policy=split filename=/dev/md127 [seq-read] rw=read -> stonewall [rand-read] rw=randread stonewall Restarting all queues made the fio job continue. There were 4 queues with state 'restart', and one queue with state 'active'. So we're missing a queue run somewhere. Cheers, Hannes -- Dr. Hannes Reinecke Teamlead Storage & Networking hare@suse.de +49 911 74053 688 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton HRB 21284 (AG Nürnberg)