From: Jan Kara <jack@suse.cz>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Laura Abbott <lauraa@codeaurora.org>,
zhuhui@xiaomi.com, minchan@kernel.org,
SeongJae Park <sj38.park@gmail.com>,
linux-mm@kvack.org, mgorman@suse.de, gioh.kim@lge.com,
lsf-pc@lists.linux-foundation.org
Subject: Re: [Lsf-pc] [LSF/MM ATTEND] Improving CMA
Date: Fri, 28 Nov 2014 10:54:31 +0100 [thread overview]
Message-ID: <20141128095431.GB25991@quack.suse.cz> (raw)
In-Reply-To: <20141128071327.GB11802@js1304-P5Q-DELUXE>
On Fri 28-11-14 16:13:27, Joonsoo Kim wrote:
> On Thu, Nov 27, 2014 at 03:12:04PM +0900, Joonsoo Kim wrote:
> > 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 also tried to solve problem from CMA, that is, reserved memory
> > utilization.
> >
> > https://lkml.org/lkml/2014/5/28/64
> >
> > While playing that patchset, I found serious problem about free page
> > counting, so I stopped to develop it for a while and tried to fix it.
> > Now, it is fixed by me and I can continue my patchset.
> >
> > https://lkml.org/lkml/2014/10/31/69
> >
> > I heard that Minchan suggests new CMA zone like movable zone, and, I
> > think that it would be the way to go. But, it would be a long-term goal
> > and I'd like to solve utilization problem with my patchset for now.
> > It is the biggest issue and it already forces someone to develop
> > out of tree solution. It's not good that out of tree solution is used
> > more and more in the product so I'd like to fix it quickly at first
> > stage.
> >
> > I think that CMA have big potential. If we fix problems of CMA
> > completely, it can be used for many places. One such case in my mind
> > is hugetlb or THP. Until now, hugetlb uses reserved approach, that is
> > very inefficient. System administrator carefully set the number of
> > reserved hugepage according to whole system workload. And application
> > can't use it freely, because it is very limited and managed resource.
> > If we use CMA for hugetlb, we can easily allocate hugepage and
> > application can use hugepages more freely.
> >
> > Anyway, I'd like to attend LSF/MM and discuss this topic.
>
> I change the subject according to LSF/MM attend request format.
> What I can do and why I'd like to attend is explained above.
> Sorry for noise.
Guys (both you and Gioh), is it such a big problem to write *new* email
(not just reply to an existing thread), use proper subject (you did this)
and write there: "I'm interested in CMA discussion, I also do X & Y". The
call for proposals specifically says "Please summarise what expertise you
will bring to the meeting". That helps us to select people when we have
more requests than space available.
I know it sounds like stupid ranting but it really makes it easier for
program committee to select people and pick up all the topic requests and
it will take you like 5 minutes max.
Honza
--
Jan Kara <jack@suse.cz>
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:[~2014-11-28 9:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 1:54 [LSF/MM TOPIC] " Laura Abbott
2014-11-25 11:32 ` [Lsf-pc] " Mel Gorman
2014-11-26 4:25 ` Gioh Kim
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 ` Jan Kara [this message]
2014-12-01 8:25 ` [Lsf-pc] " 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=20141128095431.GB25991@quack.suse.cz \
--to=jack@suse.cz \
--cc=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