All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Joonsoo Kim <js1304@gmail.com>, Johannes Weiner <hannes@cmpxchg.org>
Cc: lsf-pc@lists.linux-foundation.org,
	Linux Memory Management List <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: Thu, 28 Jan 2016 15:13:33 +0530	[thread overview]
Message-ID: <877fiu59a2.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAAmzW4OmWr1QGJn8D2c14jCPnwQ89T=YgBbg=bExgc_R6a4-bw@mail.gmail.com>

Joonsoo Kim <js1304@gmail.com> writes:

> Hello,
>
> 2016-01-23 1:38 GMT+09:00 Johannes Weiner <hannes@cmpxchg.org>:
>> 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)
>
> As far as I know, there is no disagreement on this patchset in last year LSF/MM.
> Problem may be due to my laziness... Sorry about that. I will handle it soon.
> Is there anything more that you concern?
>
>> 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
>
> I understand what Aneesh's problem is.
>
> Assume that
>
> X = non movable free page
> Y = movable free page
> Z = cma free page
>
> X < min watermark
> X + Y > high watermark
> Z > high watermark
>
> If there are bunch of consecutive movable allocation requests,
> Y will decrease. After some time, Y will be exhausted. At that
> time, there is enough Z so movable allocation request still can be
> handled in fastpath and kswapd isn't waked up. In that situation,
> if atomic non-movable page allocation for order-0 comes,
> it would be failed.
>
> Although it isn't mentioned on ZONE_CMA patchset, it is also
> fixed by that patchset because with that patchset, all CMA pages
> are in CMA zone so freepage calculation is always precise.
>

That is the issue I am hitting and if we don't have any blocker against
ZONE_CMA then we can drop this topic.

-aneesh

--
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>

  parent reply	other threads:[~2016-01-28  9:44 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
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 [this message]
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=877fiu59a2.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=hannes@cmpxchg.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=js1304@gmail.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.