From: Andrew Morton <akpm@linux-foundation.org>
To: Roman Gushchin <guro@fb.com>
Cc: Aslan Bakirov <aslan@fb.com>, Michal Hocko <mhocko@kernel.org>,
<linux-mm@kvack.org>, <kernel-team@fb.com>,
<linux-kernel@vger.kernel.org>, Rik van Riel <riel@surriel.com>,
Mike Kravetz <mike.kravetz@oracle.com>
Subject: Re: [PATCH v5 1/2] mm: cma: NUMA node interface
Date: Wed, 8 Apr 2020 17:53:12 -0700 [thread overview]
Message-ID: <20200408175312.14a055276b676edaefe636e2@linux-foundation.org> (raw)
In-Reply-To: <20200407163840.92263-2-guro@fb.com>
On Tue, 7 Apr 2020 09:38:39 -0700 Roman Gushchin <guro@fb.com> wrote:
> From: Aslan Bakirov <aslan@fb.com>
>
> I've noticed that there is no interfaces exposed by CMA which would let me
> to declare contigous memory on particular NUMA node.
>
> This patchset adds the ability to try to allocate contiguous memory on
> specific node. It will fallback to other nodes if the specified one
> doesn't work.
>
> Implement a new method for declaring contigous memory on particular node
> and keep cma_declare_contiguous() as a wrapper.
>
> Signed-off-by: Aslan Bakirov <aslan@fb.com>
> Acked-by: Michal Hocko <mhocko@kernel.org>
This should have had your signed-off-by, as you were on the patch
delivery path. Please send it along?
next prev parent reply other threads:[~2020-04-09 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 16:38 [PATCH v5 0/2] mm: using CMA for 1 GB hugepages allocation Roman Gushchin
2020-04-07 16:38 ` [PATCH v5 1/2] mm: cma: NUMA node interface Roman Gushchin
2020-04-09 0:53 ` Andrew Morton [this message]
2020-04-09 1:15 ` Roman Gushchin
2020-04-07 16:38 ` [PATCH v5 2/2] mm: hugetlb: optionally allocate gigantic hugepages using cma Roman Gushchin
2020-04-07 18:15 ` Michal Hocko
2020-04-07 18:42 ` Roman Gushchin
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=20200408175312.14a055276b676edaefe636e2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aslan@fb.com \
--cc=guro@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=riel@surriel.com \
/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