From: Jan Kara <jack@suse.cz>
To: Balbir Singh <bsingharora@gmail.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org
Subject: Re: [Lsf-pc] [LSF/MM ATTEND] 2016: Requests to attend MM-summit
Date: Fri, 22 Jan 2016 15:19:48 +0100 [thread overview]
Message-ID: <20160122141948.GG16898@quack.suse.cz> (raw)
In-Reply-To: <20160122201707.1271a279@cotter.ozlabs.ibm.com>
On Fri 22-01-16 20:17:07, Balbir Singh wrote:
> 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
I'm not really an mm guy but CMA has been discussed already last year, and
I think even the year before... Are we moving somewhere? So if this is
about hashing out what blocks VM_PINNED series (I think it may be just a
lack of Peter's persistence in pushing it ;) then that looks like a
sensible goal. Some other CMA architecture discussions need IMHO a more
concrete proposals...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
--
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 14:19 UTC|newest]
Thread overview: 13+ 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 ` Jan Kara [this message]
2016-01-22 18:18 ` [Lsf-pc] " 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
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=20160122141948.GG16898@quack.suse.cz \
--to=jack@suse.cz \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bsingharora@gmail.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 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).