linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v2] block: fix rdma queue mapping
Date: Wed, 17 Oct 2018 18:37:20 +0200	[thread overview]
Message-ID: <20181017163720.GA23798@lst.de> (raw)
In-Reply-To: <33192971-7edd-a3b6-f2fa-abdcbef375de@opengridcomputing.com>

On Wed, Oct 03, 2018@02:05:16PM -0500, Steve Wise wrote:
> Christoph, Sagi:  it seems you think /proc/irq/$IRP/smp_affinity
> shouldn't be allowed if drivers support managed affinity. Is that correct?

Not just shouldn't, but simply can't.

> But as it stands, things are just plain borked if an rdma driver
> supports ib_get_vector_affinity() yet the admin changes the affinity via
> /proc...

I think we need to fix ib_get_vector_affinity to not return anything
if the device doesn't use managed irq affinity.

  parent reply	other threads:[~2018-10-17 16:37 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
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 [this message]
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=20181017163720.GA23798@lst.de \
    --to=hch@lst.de \
    /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).