From: Michal Hocko <mhocko@suse.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Mel Gorman" <mgorman@techsingularity.net>,
"Balbir Singh" <bsingharora@gmail.com>,
linux-mm <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"Anshuman Khandual" <khandual@linux.vnet.ibm.com>,
"Aneesh Kumar KV" <aneesh.kumar@linux.vnet.ibm.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"Srikar Dronamraju" <srikar@linux.vnet.ibm.com>,
"Haren Myneni" <haren@linux.vnet.ibm.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Reza Arbab" <arbab@linux.vnet.ibm.com>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Christoph Lameter" <cl@linux.com>,
"Rik van Riel" <riel@redhat.com>
Subject: Re: [RFC summary] Enable Coherent Device Memory
Date: Wed, 17 May 2017 14:41:46 +0200 [thread overview]
Message-ID: <20170517124145.GA18988@dhcp22.suse.cz> (raw)
In-Reply-To: <1495014995.3092.20.camel@kernel.crashing.org>
On Wed 17-05-17 19:56:35, Benjamin Herrenschmidt wrote:
> On Wed, 2017-05-17 at 10:15 +0100, Mel Gorman wrote:
[...]
> > Fine -- hot add the memory from the device via a userspace trigger and
> > have the userspace trigger then setup the policies to isolate CDM from
> > general usage.
>
> This is racy though. The memory is hot added, but things can get
> allocated all over it before it has time to adjust the policies. Same
> issue we had with creating a CMA I believe.
memory hotplug is by definition 2 stage. Physical hotadd which just
prepares memory blocks and allocates struct pages and the memory online
phase. You can handle the policy part from the userspace before onlining
te first memblock from your CDM NUMA node.
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-05-17 12:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 6:18 [RFC summary] Enable Coherent Device Memory Balbir Singh
2017-05-12 10:26 ` Mel Gorman
2017-05-15 23:45 ` Balbir Singh
2017-05-16 8:43 ` Mel Gorman
2017-05-16 22:26 ` Benjamin Herrenschmidt
2017-05-17 8:28 ` Mel Gorman
2017-05-17 9:03 ` Benjamin Herrenschmidt
2017-05-17 9:15 ` Mel Gorman
2017-05-17 9:56 ` Benjamin Herrenschmidt
2017-05-17 10:58 ` Mel Gorman
2017-05-17 19:35 ` Benjamin Herrenschmidt
2017-05-17 19:37 ` Benjamin Herrenschmidt
2017-05-17 12:41 ` Michal Hocko [this message]
2017-05-17 13:54 ` Christoph Lameter
2017-05-17 19:39 ` Benjamin Herrenschmidt
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=20170517124145.GA18988@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=arbab@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bsingharora@gmail.com \
--cc=cl@linux.com \
--cc=haren@linux.vnet.ibm.com \
--cc=jglisse@redhat.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=paulmck@linux.vnet.ibm.com \
--cc=riel@redhat.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=vbabka@suse.cz \
/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).