LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>, Robert Elliott <Elliott@hp.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] blk-mq: Avoid that I/O hangs in bt_get()
Date: Thu, 06 Nov 2014 14:41:01 +0100	[thread overview]
Message-ID: <545B7A6D.8040208@acm.org> (raw)
In-Reply-To: <5433A85E.2070207@acm.org>

On 10/07/14 10:46, Bart Van Assche wrote:
> Thanks for looking into this. I can't reproduce the I/O lockup after
> having reverted my patch and after having applied your patch. In the
> test I ran fio was started with the following command-line options:
>
> fio --bs=512 --ioengine=libaio --rw=randread --buffered=0 --numjobs=12
> --iodepth=128 --iodepth_batch=64 --iodepth_batch_complete=64 --thread
> --norandommap --loops=2147483648 --runtime=3600 --group_reporting
> --gtod_reduce=1 --name=/dev/sdo --filename=/dev/sdo --invalidate=1
>
> This job was run on a system with 12 CPU threads and against a SCSI
> initiator driver for which the number of hardware contexts had been set
> to 6. Queue depth per hardware queue was set to 127:
> $ cat /sys/class/scsi_host/host10/can_queue
> 127

(replying to my own e-mail)

Hello Jens,

With kernel 3.18-rc3 and with can_queue=62 I can trigger a hang in 
bt_get() easily. The four call traces reported by echo w > 
/proc/sysrq-trigger are as follows:

Call Trace:
  [<ffffffff813d60ac>] io_schedule+0x9c/0x130
  [<ffffffff811b41bf>] bt_get+0xef/0x180
  [<ffffffff811b450f>] blk_mq_get_tag+0x9f/0xd0
  [<ffffffff811b09c6>] __blk_mq_alloc_request+0x16/0x1f0
  [<ffffffff811b1da3>] blk_mq_map_request+0x123/0x130
  [<ffffffff811b31c9>] blk_mq_make_request+0x69/0x280
  [<ffffffff811a8420>] generic_make_request+0xc0/0x110
  [<ffffffff811a84d4>] submit_bio+0x64/0x130
  [<ffffffff81147848>] do_blockdev_direct_IO+0x1dc8/0x2da0
  [<ffffffff81148867>] __blockdev_direct_IO+0x47/0x50
  [<ffffffff811435c9>] blkdev_direct_IO+0x49/0x50
  [<ffffffff810c8ce6>] generic_file_read_iter+0x546/0x610
  [<ffffffff81143962>] blkdev_read_iter+0x32/0x40
  [<ffffffff81155358>] aio_run_iocb+0x1f8/0x400
  [<ffffffff811562c1>] do_io_submit+0x121/0x490
  [<ffffffff8115663b>] SyS_io_submit+0xb/0x10
  [<ffffffff813d9612>] system_call_fastpath+0x12/0x17

Please let me know if you need more information.

Bart.

  parent reply	other threads:[~2014-11-06 13:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06 12:27 Bart Van Assche
2014-10-06 17:40 ` Jens Axboe
2014-10-06 18:53   ` Jens Axboe
2014-10-07  8:46     ` Bart Van Assche
2014-10-07 14:44       ` Jens Axboe
2014-11-06 13:41       ` Bart Van Assche [this message]
2014-12-08 14:55         ` Bart Van Assche
2014-12-08 16:49           ` Jens Axboe
2014-12-08 17:59             ` 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=545B7A6D.8040208@acm.org \
    --to=bvanassche@acm.org \
    --cc=Elliott@hp.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH] blk-mq: Avoid that I/O hangs in bt_get()' \
    /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

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).