From: Doug Ledford <dledford@redhat.com>
To: Sagi Grimberg <sagi@grimberg.me>, Jens Axboe <axboe@kernel.dk>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
linux-rdma@vger.kernel.org
Cc: Christoph Hellwig <hch@lst.de>,
Or Gerlitz <ogerlitz@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
Leon Romanovsky <leonro@mellanox.com>
Subject: Re: [PATCH v2 3/6] RDMA/core: expose affinity mappings per completion vector
Date: Fri, 28 Apr 2017 18:48:05 -0400 [thread overview]
Message-ID: <1493419685.3041.174.camel@redhat.com> (raw)
In-Reply-To: <1491474998-16423-4-git-send-email-sagi@grimberg.me>
On Thu, 2017-04-06 at 13:36 +0300, Sagi Grimberg wrote:
> This will allow ULPs to intelligently locate threads based
> on completion vector cpu affinity mappings. In case the
> driver does not expose a get_vector_affinity callout, return
> NULL so the caller can maintain a fallback logic.
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
>
Acked-by: Doug Ledford <dledford@redhat.com>
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
WARNING: multiple messages have this Message-ID (diff)
From: dledford@redhat.com (Doug Ledford)
Subject: [PATCH v2 3/6] RDMA/core: expose affinity mappings per completion vector
Date: Fri, 28 Apr 2017 18:48:05 -0400 [thread overview]
Message-ID: <1493419685.3041.174.camel@redhat.com> (raw)
In-Reply-To: <1491474998-16423-4-git-send-email-sagi@grimberg.me>
On Thu, 2017-04-06@13:36 +0300, Sagi Grimberg wrote:
> This will allow ULPs to intelligently locate threads based
> on completion vector cpu affinity mappings. In case the
> driver does not expose a get_vector_affinity callout, return
> NULL so the caller can maintain a fallback logic.
>
> Reviewed-by: Christoph Hellwig <hch at lst.de>
> Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
>?
Acked-by: Doug Ledford <dledford at redhat.com>
--
Doug Ledford <dledford at redhat.com>
? ? GPG KeyID: B826A3330E572FDD
? ?
Key fingerprint = AE6B 1BDA 122B 23B4 265B ?1274 B826 A333 0E57 2FDD
next prev parent reply other threads:[~2017-04-28 22:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 10:36 [PATCH v2 0/6] Automatic affinity settings for nvme over rdma Sagi Grimberg
2017-04-06 10:36 ` Sagi Grimberg
2017-04-06 10:36 ` [PATCH v2 1/6] mlx5: convert to generic pci_alloc_irq_vectors Sagi Grimberg
2017-04-06 10:36 ` Sagi Grimberg
2017-04-06 14:24 ` Leon Romanovsky
2017-04-06 14:24 ` Leon Romanovsky
2017-04-06 14:24 ` Leon Romanovsky
2017-04-06 10:36 ` [PATCH v2 2/6] mlx5: move affinity hints assignments to generic code Sagi Grimberg
2017-04-06 10:36 ` Sagi Grimberg
2017-04-06 10:36 ` Sagi Grimberg
2017-04-06 14:27 ` Leon Romanovsky
2017-04-06 14:27 ` Leon Romanovsky
2017-04-06 14:27 ` Leon Romanovsky
2017-04-06 10:36 ` [PATCH v2 3/6] RDMA/core: expose affinity mappings per completion vector Sagi Grimberg
2017-04-06 10:36 ` Sagi Grimberg
2017-04-28 22:48 ` Doug Ledford [this message]
2017-04-28 22:48 ` Doug Ledford
2017-05-03 8:02 ` Sagi Grimberg
2017-05-03 8:02 ` Sagi Grimberg
2017-05-03 10:34 ` Håkon Bugge
2017-05-03 10:34 ` Håkon Bugge
2017-05-03 10:34 ` Håkon Bugge
2017-04-06 10:36 ` [PATCH v2 4/6] mlx5: support ->get_vector_affinity Sagi Grimberg
2017-04-06 10:36 ` Sagi Grimberg
2017-04-06 14:30 ` Leon Romanovsky
2017-04-06 14:30 ` Leon Romanovsky
2017-04-06 14:30 ` Leon Romanovsky
2017-04-06 10:36 ` [PATCH v2 5/6] block: Add rdma affinity based queue mapping helper Sagi Grimberg
2017-04-06 10:36 ` Sagi Grimberg
2017-04-06 10:36 ` [PATCH v2 6/6] nvme-rdma: use intelligent affinity based queue mappings Sagi Grimberg
2017-04-06 10:36 ` Sagi Grimberg
2017-04-23 12:01 ` [PATCH v2 0/6] Automatic affinity settings for nvme over rdma Sagi Grimberg
2017-04-23 12:01 ` 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=1493419685.3041.174.camel@redhat.com \
--to=dledford@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=leonro@mellanox.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-rdma@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=saeedm@mellanox.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 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.