All of lore.kernel.org
 help / color / mirror / Atom feed
From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH 0/2] nvme: NUMA locality for fabrics
Date: Fri,  5 Oct 2018 11:29:13 +0200	[thread overview]
Message-ID: <20181005092915.126636-1-hare@suse.de> (raw)

Hi all,

[Resend, as I forgot to include the nvme ml]

here's a patchset to leverage NUMA locality information for fabric controllers.
As there are systems for which no 'best' configuration exists (eg a symmetric
NUMA machine with 4 nodes and 2 HBAs) it also exports the node mapping to
sysfs so that the admin can tweak them to achieve best performance.

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.

Hannes Reinecke (2):
  nvme: NUMA locality information for fabrics
  nvme-multipath: manual NUMA configuration

 drivers/nvme/host/core.c      | 68 +++++++++++++++++++++++++++++++++++++++++--
 drivers/nvme/host/fc.c        |  5 ++--
 drivers/nvme/host/multipath.c | 11 +++++--
 drivers/nvme/host/nvme.h      |  3 ++
 drivers/nvme/host/pci.c       |  2 +-
 drivers/nvme/host/rdma.c      |  6 ++--
 6 files changed, 85 insertions(+), 10 deletions(-)

-- 
2.16.4

             reply	other threads:[~2018-10-05  9:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05  9:29 Hannes Reinecke [this message]
2018-10-05  9:29 ` [PATCH 1/2] nvme: NUMA locality information for fabrics Hannes Reinecke
2018-10-08 10:04   ` Christoph Hellwig
2018-10-08 10:22     ` Matias Bjørling
2018-10-08 10:27       ` Hannes Reinecke
2018-10-08 10:29         ` Matias Bjørling
2018-10-08 23:29           ` Sagi Grimberg
2018-10-08 23:31             ` Sagi Grimberg
2018-10-09  6:14             ` Hannes Reinecke
2018-10-09  6:13       ` Christoph Hellwig
2018-10-08 10:24     ` Hannes Reinecke
2018-10-05  9:29 ` [PATCH 2/2] nvme-multipath: manual NUMA configuration Hannes Reinecke
2018-10-08 10:05   ` Christoph Hellwig
2018-10-08 10:19     ` Hannes Reinecke

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=20181005092915.126636-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.