From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: take node locality into account when selecting a path
Date: Mon, 1 Oct 2018 00:59:07 +0200 [thread overview]
Message-ID: <20180930225907.GA20144@lst.de> (raw)
In-Reply-To: <0bd80d4b-3ae8-a9e2-c19b-5531fbfac8b3@suse.de>
On Sat, Sep 29, 2018@02:09:15PM +0200, Hannes Reinecke wrote:
> Actually I would love to have some statistic or debug info showing the
> NUMA locality mapping somewhere. Otherwise the admin might have a hard
> time figuring out what's going on here, plus debugging any I/O routing
> issues will be tricky.
You already see the node of the devices in sysfs, so what else do you
think of?
prev parent reply other threads:[~2018-09-30 22:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 23:05 [PATCH] nvme: take node locality into account when selecting a path Christoph Hellwig
2018-09-28 14:12 ` Keith Busch
2018-09-28 22:31 ` Sagi Grimberg
2018-09-30 23:01 ` Christoph Hellwig
2018-10-01 19:45 ` Sagi Grimberg
2018-10-02 17:30 ` Hannes Reinecke
2018-10-02 17:39 ` Christoph Hellwig
2018-10-03 8:56 ` Hannes Reinecke
2018-10-03 12:43 ` Christoph Hellwig
2018-10-04 1:30 ` Sagi Grimberg
2018-10-04 15:40 ` Hannes Reinecke
2018-09-29 12:09 ` Hannes Reinecke
2018-09-30 22:59 ` Christoph Hellwig [this message]
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=20180930225907.GA20144@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).