From: Johannes Weiner <hannes@cmpxchg.org>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [LSF/MM ATTEND] 2016: Requests to attend MM-summit
Date: Fri, 22 Jan 2016 11:38:01 -0500 [thread overview]
Message-ID: <20160122163801.GA16668@cmpxchg.org> (raw)
In-Reply-To: <87k2n2usyf.fsf@linux.vnet.ibm.com>
Hi,
On Fri, Jan 22, 2016 at 10:11:12AM +0530, Aneesh Kumar K.V wrote:
> * CMA allocator issues:
> (1) order zero allocation failures:
> We are observing order zero non-movable allocation failures in kernel
> with CMA configured. We don't start a reclaim because our free memory check
> does not consider free_cma. Hence the reclaim code assume we have enough free
> pages. Joonsoo Kim tried to fix this with his ZOME_CMA patches. I would
> like to discuss the challenges in getting this merged upstream.
> https://lkml.org/lkml/2015/2/12/95 (ZONE_CMA)
The exclusion of cma pages from the watermark checks means that
reclaim is happening too early, not too late, which leaves memory
underutilized. That's what ZONE_CMA set out to fix.
But unmovable allocations can still fail when the only free memory is
inside CMA regions. I don't see how ZONE_CMA would fix that.
CC Joonsoo
But as Jan said, we discussed ZONE_CMA before, so it's not clear
whether rehashing it without new data points would be too useful.
> Others needed for the discussion:
> Joonsoo Kim <iamjoonsoo.kim@lge.com>
>
> (2) CMA allocation failures due to pinned pages in the region:
> We allow only movable allocation from the CMA region to enable us
> to migrate those pages later when we get a CMA allocation request. But
> if we pin those movable pages, we will fail the migration which can result
> in CMA allocation failure. One such report can be found here.
> http://article.gmane.org/gmane.linux.kernel.mm/136738
>
> Peter Zijlstra's VM_PINNED patch series should help in fixing the issue. I would
> like to discuss what needs to be done to get this patch series merged upstream
> https://lkml.org/lkml/2014/5/26/345 (VM_PINNED)
>
> Others needed for the discussion:
> Peter Zijlstra <peterz@infradead.org>
There was no consensus whether this specific implementation would work
well for all sources of pinning. Giving this some time in the MM track
could be useful.
CC Peter
--
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:[~2016-01-22 16:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 4:41 [LSF/MM ATTEND] 2016: Requests to attend MM-summit Aneesh Kumar K.V
2016-01-22 9:17 ` Balbir Singh
2016-01-22 14:19 ` [Lsf-pc] " Jan Kara
2016-01-22 18:18 ` Laura Abbott
2016-01-27 19:07 ` Vlastimil Babka
2016-01-28 9:33 ` Aneesh Kumar K.V
2016-01-22 16:38 ` Johannes Weiner [this message]
2016-01-25 7:08 ` Joonsoo Kim
2016-01-25 23:37 ` Laura Abbott
2016-01-26 7:38 ` Joonsoo Kim
2016-01-26 18:53 ` Vlastimil Babka
2016-01-28 9:43 ` Aneesh Kumar K.V
2016-01-27 18:32 ` Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2016-01-12 16:05 LSF/MM 2016: Call for Proposals Martin K. Petersen
2016-01-15 8:10 ` [LSF/MM ATTEND] 2016: Requests to attend MM-summit Jesper Dangaard Brouer
2016-01-15 8:10 ` Jesper Dangaard Brouer
2016-01-15 16:49 ` Christoph Lameter
2016-01-15 16:49 ` Christoph Lameter
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=20160122163801.GA16668@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=peterz@infradead.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.