All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <bsingharora@gmail.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [LSF/MM ATTEND] 2016: Requests to attend MM-summit
Date: Fri, 22 Jan 2016 20:17:07 +1100	[thread overview]
Message-ID: <20160122201707.1271a279@cotter.ozlabs.ibm.com> (raw)
In-Reply-To: <87k2n2usyf.fsf@linux.vnet.ibm.com>

On Fri, 22 Jan 2016 10:11:12 +0530
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> wrote:

> Hi,
> 
> I would like to attend LSF/MM this year (2016).
> 
> My main interest is in MM related topics although I am also interested
> in the btrfs status discussion (particularly related to subpage size block
> size topic), if we are having one. Most of my recent work in the kernel is
> related to adding ppc64 support for different MM features. My current focus
> is on adding Linux support for the new radix MMU model of Power9.
> 
> Topics of interest include:
> 
> * 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)
> 
> 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>

+1

I agree CMA design is a concern. I also noticed that today all CMA pages come
from one node. On a NUMA box you'll see cross traffic going to that region -
although from kernel only text. It should be discussed at the summit and Aneesh
would be a good representative

Balbir Singh.

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

  reply	other threads:[~2016-01-22  9:17 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 [this message]
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
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=20160122201707.1271a279@cotter.ozlabs.ibm.com \
    --to=bsingharora@gmail.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.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.