From: hare@suse.de (Hannes Reinecke)
Subject: [PATCHv3 0/3] nvme: NUMA locality for fabrics
Date: Fri, 2 Nov 2018 10:56:38 +0100 [thread overview]
Message-ID: <20181102095641.28504-1-hare@suse.de> (raw)
Hi all,
here's a patchset to leverage NUMA locality information for fabric controllers.
This is the second attempt for doing so; after discussion with hch we came
to the conclusion that the attempt in the initial submission with a manual
configuration would only lead to more confusion and suboptimal configuration.
So here's now a version with an automatic NUMA balancing, where we attempt
to split the number submitting CPUs/cores evenly across the available
controller.
With this patchset I'm seeing a performance increase from
262k IOPS to 344k IOPS, measured against a NetApp AF700.
As usual, comments and reviews are welcome.
Changes to v2:
- use 'numa_node' instead of 'node_id' (suggested by Sagi)
- rediff patches for better readability
Hannes Reinecke (3):
nvme: NUMA locality information for fabrics
nvme-multipath: Select paths based on NUMA locality
nvme-multipath: automatic NUMA path balancing
drivers/nvme/host/core.c | 36 ++++++++++++-
drivers/nvme/host/fc.c | 5 +-
drivers/nvme/host/multipath.c | 119 +++++++++++++++++++++++++++++++++++++++++-
drivers/nvme/host/nvme.h | 3 ++
drivers/nvme/host/rdma.c | 6 ++-
5 files changed, 161 insertions(+), 8 deletions(-)
--
2.16.4
next reply other threads:[~2018-11-02 9:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 9:56 Hannes Reinecke [this message]
2018-11-02 9:56 ` [PATCH 1/3] nvme: NUMA locality information for fabrics Hannes Reinecke
2018-11-08 9:22 ` Christoph Hellwig
2018-11-08 9:35 ` Hannes Reinecke
2018-11-02 9:56 ` [PATCH 2/3] nvme-multipath: Select paths based on NUMA locality Hannes Reinecke
2018-11-08 9:32 ` Christoph Hellwig
2018-11-02 9:56 ` [PATCH 3/3] nvme-multipath: automatic NUMA path balancing Hannes Reinecke
2018-11-08 9:36 ` Christoph Hellwig
2018-11-16 8:12 ` [PATCHv3 0/3] nvme: NUMA locality for fabrics Christoph Hellwig
2018-11-16 8:21 ` Hannes Reinecke
2018-11-16 8:23 ` Christoph Hellwig
2018-11-19 22:31 ` Sagi Grimberg
2018-11-20 6:12 ` Hannes Reinecke
2018-11-20 9:41 ` Christoph Hellwig
2018-11-20 15:47 ` Keith Busch
2018-11-20 19:27 ` James Smart
2018-11-21 8:36 ` Christoph Hellwig
2018-11-20 16:21 ` Hannes Reinecke
2018-11-20 18:12 ` James Smart
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=20181102095641.28504-1-hare@suse.de \
--to=hare@suse.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 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.