From: swise@opengridcomputing.com (Steve Wise)
Subject: crash when connecting to targets using nr_io_queues < num cpus
Date: Thu, 1 Sep 2016 09:10:56 -0500 [thread overview]
Message-ID: <00ae01d2045a$a8516500$f8f42f00$@opengridcomputing.com> (raw)
In-Reply-To: <6082d700-a45c-b00a-3f09-ba6196cc3e5e@grimberg.me>
>
> > Hey all,
> >
> > I'm testing smaller ioq sets with nvmf/rdma, and I see some issue. If I
connect
> > with 2, 4, 6, 8, 10, 16, or 32 for nr_io_queues, everything is happy. It
> > seems, though, if I connect with a value of 12, or 28, or some other non
power
> > of two, I get intermittent crashes in __blk_mq_get_reserved_tag() at line
337
> > when setting up a controller's IO queues. I'm not sure exactly if this is
> > always non power of two, or something else, but it seems to never crash with
> > power of two values (could be a coincidence I guess).
>
> I think Ming sent a patch for this some time ago... Not sure what
> happened with it though...
This?
http://lists.infradead.org/pipermail/linux-nvme/2016-June/004884.html
next prev parent reply other threads:[~2016-09-01 14:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 20:12 crash when connecting to targets using nr_io_queues < num cpus Steve Wise
2016-09-01 9:32 ` Sagi Grimberg
2016-09-01 14:10 ` Steve Wise [this message]
2016-09-01 19:01 ` Steve Wise
2016-09-04 8:46 ` Sagi Grimberg
2016-09-13 14:21 ` Steve Wise
2016-09-13 17:14 ` Ming Lin
2016-09-13 17:52 ` Keith Busch
2016-09-13 19:43 ` Steve Wise
2016-09-16 14:10 ` Steve Wise
2016-09-16 14:26 ` 'Christoph Hellwig'
2016-09-22 21:02 ` 'Christoph Hellwig'
2016-09-22 21:38 ` Steve Wise
2016-09-22 21:48 ` 'Christoph Hellwig'
2016-09-22 22:03 ` Steve Wise
[not found] ` <024201d2151d$28013b90$7803b2b0$@opengridcomputing.com>
2016-09-23 0:01 ` Steve Wise
2016-09-23 3:31 ` 'Christoph Hellwig'
2016-09-23 13:58 ` Steve Wise
2016-09-23 16:21 ` Jens Axboe
2016-09-23 16:23 ` 'Christoph Hellwig'
2016-09-23 16:24 ` Jens Axboe
2016-09-23 16:26 ` Jens Axboe
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='00ae01d2045a$a8516500$f8f42f00$@opengridcomputing.com' \
--to=swise@opengridcomputing.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.