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,
intel-wired-lan@lists.osuosl.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: [RFC] mm: Replace all open encodings for NUMA_NO_NODE
Date: Mon, 12 Nov 2018 09:40:39 +0530 [thread overview]
Message-ID: <b92e3275-7a04-a148-bb5b-38658c270583@arm.com> (raw)
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 ?
WARNING: multiple messages have this Message-ID (diff)
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,
intel-wired-lan@lists.osuosl.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:40:39 +0530 [thread overview]
Message-ID: <b92e3275-7a04-a148-bb5b-38658c270583@arm.com> (raw)
In-Reply-To: <1e9393c5-ff43-8ec7-dd6c-a662f09ef7c1@gmail.com>
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 ?
WARNING: multiple messages have this Message-ID (diff)
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,
intel-wired-lan@lists.osuosl.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 04:22:39 +0000 [thread overview]
Message-ID: <b92e3275-7a04-a148-bb5b-38658c270583@arm.com> (raw)
In-Reply-To: <1541990515-11670-1-git-send-email-anshuman.khandual@arm.com>
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 ?
WARNING: multiple messages have this Message-ID (diff)
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Joseph Qi <jiangqi903@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: linux-fbdev@vger.kernel.org, linux-ia64@vger.kernel.org,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-block@vger.kernel.org,
sparclinux@vger.kernel.org, iommu@lists.linux-foundation.org,
intel-wired-lan@lists.osuosl.org, linux-alpha@vger.kernel.org,
dmaengine@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
ocfs2-devel@oss.oracle.com, linux-media@vger.kernel.org
Subject: Re: [RFC] mm: Replace all open encodings for NUMA_NO_NODE
Date: Mon, 12 Nov 2018 09:40:39 +0530 [thread overview]
Message-ID: <b92e3275-7a04-a148-bb5b-38658c270583@arm.com> (raw)
In-Reply-To: <1e9393c5-ff43-8ec7-dd6c-a662f09ef7c1@gmail.com>
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 ?
WARNING: multiple messages have this Message-ID (diff)
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [RFC] mm: Replace all open encodings for NUMA_NO_NODE
Date: Mon, 12 Nov 2018 09:40:39 +0530 [thread overview]
Message-ID: <b92e3275-7a04-a148-bb5b-38658c270583@arm.com> (raw)
In-Reply-To: <1e9393c5-ff43-8ec7-dd6c-a662f09ef7c1@gmail.com>
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 ?
next reply other threads:[~2018-11-12 4:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 4:10 Anshuman Khandual [this message]
2018-11-12 4:22 ` [RFC] mm: Replace all open encodings for NUMA_NO_NODE Anshuman Khandual
2018-11-12 4:10 ` [Intel-wired-lan] " Anshuman Khandual
2018-11-12 4:10 ` Anshuman Khandual
2018-11-12 4:10 ` Anshuman Khandual
-- strict thread matches above, loose matches on Subject: below --
2018-11-12 11:47 Anshuman Khandual
2018-11-12 11:59 ` Anshuman Khandual
2018-11-12 11:47 ` [Intel-wired-lan] " Anshuman Khandual
2018-11-12 11:47 ` Anshuman Khandual
2018-11-12 11:47 ` Anshuman Khandual
2018-11-12 8:43 Hans Verkuil
2018-11-12 8:43 ` [Intel-wired-lan] " Hans Verkuil
2018-11-12 8:43 ` Hans Verkuil
2018-11-12 8:43 ` Hans Verkuil
2018-11-12 8:43 ` Hans Verkuil
2018-11-12 8:43 ` Hans Verkuil
2018-11-12 4:14 Anshuman Khandual
2018-11-12 4:26 ` Anshuman Khandual
2018-11-12 4:14 ` Anshuman Khandual
2018-11-12 4:14 ` Anshuman Khandual
2018-11-12 3:57 Joseph Qi
2018-11-12 3:57 ` [Intel-wired-lan] " Joseph Qi
2018-11-12 3:57 ` Joseph Qi
2018-11-12 3:57 ` [Ocfs2-devel] " Joseph Qi
2018-11-12 3:57 ` Joseph Qi
2018-11-12 3:57 ` Joseph Qi
2018-11-12 2:41 Anshuman Khandual
2018-11-12 2:53 ` Anshuman Khandual
2018-11-12 2:41 ` [Intel-wired-lan] " Anshuman Khandual
2018-11-12 2:41 ` Anshuman Khandual
2018-11-12 2:41 ` 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=b92e3275-7a04-a148-bb5b-38658c270583@arm.com \
--to=anshuman.khandual@arm.com \
--cc=dmaengine@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-wired-lan@lists.osuosl.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 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.