From: Michal Hocko <mhocko@kernel.org>
To: Aslan Bakirov <aslanbekirov@gmail.com>
Cc: Ira Weiny <ira.weiny@intel.com>, Aslan Bakirov <aslan@fb.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, kernel-team@fb.com, riel@surriel.com,
Roman Gushchin <guro@fb.com>,
hannes@cmpxchg.org
Subject: Re: [PATCH v3] mm: cma: NUMA node interface
Date: Fri, 3 Apr 2020 12:01:20 +0200 [thread overview]
Message-ID: <20200403100120.GY22681@dhcp22.suse.cz> (raw)
In-Reply-To: <CAJth39gjy34swBqVUy7mOo0-Dbxzb5TZn2jUNsrcq8iHpK_ToA@mail.gmail.com>
On Fri 03-04-20 10:51:32, Aslan Bakirov wrote:
> On Fri, Apr 3, 2020 at 6:02 AM Ira Weiny <ira.weiny@intel.com> wrote:
>
> > On Thu, Apr 02, 2020 at 07:12:56PM -0700, Aslan Bakirov wrote:
> > > 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.
> >
> > Is there an additional patch which uses this new interface?
> >
> > Generally the patch seems reasonable but we should have a user.
>
>
> Thanks for the comments. Yes, actually, this is the version 3 of first
> patch ([PATCH 1/2] mm: cma: NUMA node interface)
> of patchset. Second patch, which uses this interface is "[PATCH 2/2] mm:
> hugetlb: Use node interface of cma"
It would have been much more clear to send those two patches together as
you can see.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-04-03 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 2:12 Aslan Bakirov
2020-04-03 5:02 ` Ira Weiny
2020-04-03 9:51 ` Aslan Bakirov
2020-04-03 10:01 ` Michal Hocko [this message]
2020-04-03 10:21 ` Aslan Bakirov
-- strict thread matches above, loose matches on Subject: below --
2020-04-02 23:22 Aslan Bakirov
2020-04-03 0:27 ` Matthew Wilcox
2020-04-03 2:19 ` Aslan Bakirov
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=20200403100120.GY22681@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aslan@fb.com \
--cc=aslanbekirov@gmail.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=ira.weiny@intel.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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