From: Gioh Kim <gioh.kim@lge.com>
To: Mel Gorman <mgorman@suse.de>, Laura Abbott <lauraa@codeaurora.org>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
SeongJae Park <sj38.park@gmail.com>,
minchan@kernel.org, zhuhui@xiaomi.com, iamjoonsoo.kim@lge.com
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] Improving CMA
Date: Wed, 26 Nov 2014 13:25:05 +0900 [thread overview]
Message-ID: <54755621.6050700@lge.com> (raw)
In-Reply-To: <20141125113225.GH2725@suse.de>
2014-11-25 i??i?? 8:32i?? Mel Gorman i?'(e??) i?' e,?:
> On Mon, Nov 24, 2014 at 05:54:14PM -0800, Laura Abbott wrote:
>> There have been a number of patch series posted designed to improve various
>> aspects of CMA. A sampling:
>>
>> https://lkml.org/lkml/2014/10/15/623
>> http://marc.info/?l=linux-mm&m=141571797202006&w=2
>> https://lkml.org/lkml/2014/6/26/549
>>
>> As far as I can tell, these are all trying to fix real problems with CMA but
>> none of them have moved forward very much from what I can tell. The goal of
>> this session would be to come out with an agreement on what are the biggest
>> problems with CMA and the best ways to solve them.
>>
>
> I think this is a good topic. Some of the issues have been brought up before
> at LSF/MM but they never made that much traction so it's worth revisiting. I
> haven't been paying close attention to the mailing list discussions but
> I've been a little worried that the page allocator paths are turning into
> a bigger and bigger mess. I'm also a bit worried that options such as
> migrating pages out of CMA areas that are about to be pinned for having
> callback options to forcibly free pages never went anywhere.
>
I have two question.
First, is GCMA able to replace CMA? It's news to me.
I need some time to check GCMA.
Second, is CMA popular enough to change allocator path?
Yes, I need it.
But I don't know any company uses it, and nobody seems to have interest in it.
--
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:[~2014-11-26 4:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 1:54 [LSF/MM TOPIC] Improving CMA Laura Abbott
2014-11-25 11:32 ` [Lsf-pc] " Mel Gorman
2014-11-26 4:25 ` Gioh Kim [this message]
2014-11-26 5:56 ` SeongJae Park
2014-11-26 5:58 ` 答复: " 朱辉
2014-11-26 18:29 ` Laura Abbott
2014-11-26 6:46 ` Minchan Kim
2014-11-27 6:12 ` Joonsoo Kim
2014-11-27 7:43 ` Gioh Kim
2014-11-28 7:15 ` [LSF/MM ATTEND] " Gioh Kim
2014-11-28 7:13 ` Joonsoo Kim
2014-11-28 9:54 ` [Lsf-pc] " Jan Kara
2014-12-01 8:25 ` Joonsoo Kim
2014-11-30 23:54 ` Gioh Kim
2014-11-27 7:56 ` [LSF/MM TOPIC] " Wanpeng Li
2014-11-27 16:11 ` [Lsf-pc] " James Bottomley
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=54755621.6050700@lge.com \
--to=gioh.kim@lge.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=lauraa@codeaurora.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=sj38.park@gmail.com \
--cc=zhuhui@xiaomi.com \
/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).