linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Steve Wise" <swise@opengridcomputing.com>
To: "'Sagi Grimberg'" <sagi@grimberg.me>, "'Ming Lei'" <ming.lei@redhat.com>
Cc: linux-rdma@vger.kernel.org, linux-block@vger.kernel.org,
	'Christoph Hellwig' <hch@lst.de>,
	linux-nvme@lists.infradead.org,
	'Max Gurtovoy' <maxg@mellanox.com>
Subject: RE: [PATCH v2] block: fix rdma queue mapping
Date: Sat, 25 Aug 2018 07:18:43 -0500	[thread overview]
Message-ID: <005801d43c6d$c4afbba0$4e0f32e0$@opengridcomputing.com> (raw)
In-Reply-To: <e82f994b-76ec-2a04-b575-acb4439e4d5b@grimberg.me>

> > I guess this way still can't fix the request allocation crash issue
> > triggered by using blk_mq_alloc_request_hctx(), in which one hw queue
> may
> > not be mapped from any online CPU.
> 
> Not really. I guess we will need to simply skip queues that are
> mapped to an offline cpu.
> 
> > Maybe this patch isn't for this issue, but it is closely related.
> 
> Yes, another patch is still needed.
> 
> Steve, do you still have that patch? I don't seem to
> find it anywhere.

I have no such patch.  I don't remember this issue.

Steve.


_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2018-08-25 12:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20 20:54 [PATCH v2] block: fix rdma queue mapping Sagi Grimberg
2018-08-21  2:04 ` Ming Lei
2018-08-25  2:06   ` Sagi Grimberg
2018-08-25 12:18     ` Steve Wise [this message]
2018-08-27  3:50       ` Ming Lei
2018-08-22 13:11 ` Christoph Hellwig
2018-08-25  2:17   ` Sagi Grimberg
2018-10-03 19:05     ` Steve Wise
2018-10-03 21:14       ` Sagi Grimberg
2018-10-03 21:21         ` Steve Wise
2018-10-16  1:04         ` Sagi Grimberg
2018-10-17 16:37           ` Christoph Hellwig
2018-10-17 16:37       ` Christoph Hellwig
2018-10-23  6:02         ` Sagi Grimberg
2018-10-23 13:00           ` Steve Wise
2018-10-23 21:25             ` Sagi Grimberg
2018-10-23 21:31               ` Steve Wise
2018-10-24  0:09               ` Shiraz Saleem
2018-10-24  0:37                 ` Sagi Grimberg
2018-10-29 23:58                   ` Saleem, Shiraz
2018-10-30 18:26                     ` Sagi Grimberg

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='005801d43c6d$c4afbba0$4e0f32e0$@opengridcomputing.com' \
    --to=swise@opengridcomputing.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=maxg@mellanox.com \
    --cc=ming.lei@redhat.com \
    --cc=sagi@grimberg.me \
    /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).