From: Peng Liu <liupeng256@huawei.com>
To: <bhelgaas@google.com>, <tglx@linutronix.de>, <mingo@redhat.com>,
<bp@alien8.de>, <dave.hansen@linux.intel.com>, <x86@kernel.org>,
<hpa@zytor.com>, <lorenzo.pieralisi@arm.com>,
<guohanjun@huawei.com>, <sudeep.holla@arm.com>,
<rafael@kernel.org>, <lenb@kernel.org>,
<akpm@linux-foundation.org>, <logang@deltatee.com>,
<martin.oliveira@eideticom.com>, <thunder.leizhen@huawei.com>,
<axboe@kernel.dk>, <kch@nvidia.com>, <ming.lei@redhat.com>,
<shinichiro.kawasaki@wdc.com>, <mcgrof@kernel.org>,
<jiangguoqing@kylinos.cn>, <jpittman@redhat.com>,
<dave@stgolabs.net>, <liupeng256@huawei.com>,
<wangkefeng.wang@huawei.com>, <linux-block@vger.kernel.org>,
<linux-ia64@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-pci@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <linux-mm@kvack.org>
Subject: [PATCH 0/2] null_blk: fix wrong use of nr_online_nodes
Date: Fri, 6 May 2022 01:57:59 +0000 [thread overview]
Message-ID: <20220506015801.757918-1-liupeng256@huawei.com> (raw)
Helper node_available is introduced to judge whether a node can be
used, and it is used to fix the wrong use of nr_online_nodes when
numa node is sparse.
Peng Liu (2):
include/linux/nodemask.h: create node_available() helper
null_blk: fix wrong use of nr_online_nodes
arch/ia64/hp/common/sba_iommu.c | 2 +-
arch/x86/pci/acpi.c | 2 +-
drivers/acpi/arm64/iort.c | 2 +-
drivers/block/null_blk/main.c | 45 ++++++++++++++++++++-------------
drivers/pci/pci-sysfs.c | 2 +-
include/linux/nodemask.h | 3 +++
mm/mempolicy.c | 2 +-
7 files changed, 36 insertions(+), 22 deletions(-)
--
2.25.1
next reply other threads:[~2022-05-06 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 1:57 Peng Liu [this message]
2022-05-06 1:58 ` [PATCH 1/2] include/linux/nodemask.h: create node_available() helper Peng Liu
2022-05-06 17:23 ` Bjorn Helgaas
2022-05-06 1:58 ` [PATCH 2/2] null_blk: fix wrong use of nr_online_nodes Peng Liu
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=20220506015801.757918-1-liupeng256@huawei.com \
--to=liupeng256@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=guohanjun@huawei.com \
--cc=hpa@zytor.com \
--cc=jiangguoqing@kylinos.cn \
--cc=jpittman@redhat.com \
--cc=kch@nvidia.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=martin.oliveira@eideticom.com \
--cc=mcgrof@kernel.org \
--cc=ming.lei@redhat.com \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=sudeep.holla@arm.com \
--cc=tglx@linutronix.de \
--cc=thunder.leizhen@huawei.com \
--cc=wangkefeng.wang@huawei.com \
--cc=x86@kernel.org \
/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).