From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Joseph Qi <jiangqi903@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: ocfs2-devel@oss.oracle.com, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org, netdev@vger.kernel.org,
linux-media@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-rdma@vger.kernel.org, dmaengine@vger.kernel.org,
linux-block@vger.kernel.org, sparclinux@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-ia64@vger.kernel.org,
linux-alpha@vger.kernel.org
Subject: Re: [RFC] mm: Replace all open encodings for NUMA_NO_NODE
Date: Mon, 12 Nov 2018 09:44:32 +0530 [thread overview]
Message-ID: <926057f3-f31d-9fe0-e2a8-d76bc3d97049@arm.com> (raw)
In-Reply-To: <b92e3275-7a04-a148-bb5b-38658c270583@arm.com>
On 11/12/2018 09:40 AM, Anshuman Khandual wrote:
>
>
> On 11/12/2018 09:27 AM, Joseph Qi wrote:
>> For ocfs2 part, node means host in the cluster, not NUMA node.
>>
>
> Does not -1 indicate an invalid node which can never be present ?
>
My bad, got it wrong. Seems like this is nothing to do with NUMA node
at all. Will drop the changes from ocfs2.
next prev parent reply other threads:[~2018-11-12 4:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 2:41 Anshuman Khandual
2018-11-12 3:57 ` Joseph Qi
2018-11-12 4:10 ` Anshuman Khandual
2018-11-12 4:14 ` Anshuman Khandual [this message]
2018-11-12 8:43 ` Hans Verkuil
2018-11-12 11:47 ` Anshuman Khandual
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=926057f3-f31d-9fe0-e2a8-d76bc3d97049@arm.com \
--to=anshuman.khandual@arm.com \
--cc=dmaengine@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jiangqi903@gmail.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=sparclinux@vger.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