linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: swise@opengridcomputing.com (Steve Wise)
Subject: crash when connecting to targets using nr_io_queues < num cpus
Date: Tue, 13 Sep 2016 14:43:42 -0500	[thread overview]
Message-ID: <020501d20df7$21ccd180$65667480$@opengridcomputing.com> (raw)
In-Reply-To: <20160913175223.GB13741@localhost.localdomain>

> > > >>> 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
> > > >
> > > > This is indeed the same problem.  I don't have the knoggin to propose a
fix.
> > > > Sagi/Christoph, do you have any ideas on this?  I'm willing to take and
idea
> > > > forward and test it out of you all have any clever ideas.  We should at
> > least
> > > > prevent setting nr_io_queues to a value that will crash immediately when
> > nvmf is
> > > > used...
> > >
> > > I think that Ming and Keith had a few suggestions.
> > >
> > > ++ Keith.
> > >
> >
> > Ming has been silent. :(  Keith, any thoughts on this?
> 
> Sorry, I've also been side tracked. :(
> 
> Offline, I've been reviewing and testing new mappings from Christoph
> and Thomas that should get all the queues assigned. It wasn't developed
> specically for this issue, but it should fix this anyway. I think the
> new mapping is really close to being ready for public consideration,
> but I'll wait for Christoph on that.

Hey Keith,

Sounds good.  I can test any proposed patches...

Thanks,

Steve.

  reply	other threads:[~2016-09-13 19:43 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
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 [this message]
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='020501d20df7$21ccd180$65667480$@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 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).