linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Gioh Kim <gioh.kim@lge.com>
To: Laura Abbott <lauraa@codeaurora.org>, Jan Kara <jack@suse.cz>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	zhuhui@xiaomi.com, minchan@kernel.org,
	SeongJae Park <sj38.park@gmail.com>,
	linux-mm@kvack.org, mgorman@suse.de,
	lsf-pc@lists.linux-foundation.org
Subject: [Lsf-pc] [LSF/MM ATTEND] Improving CMA
Date: Mon, 01 Dec 2014 08:54:36 +0900	[thread overview]
Message-ID: <547BAE3C.5020309@lge.com> (raw)
In-Reply-To: <20141128071327.GB11802@js1304-P5Q-DELUXE>


I'm very sorry for causing noise.

I wanted to use CMA for 2 applications:
1. power saving: clear one ddr chip and turn off power
2. memory allocation for device: GPU and video and so on

At first I've tested CMA for power saving with 2 out-of-tree patches:
1. https://lkml.org/lkml/2012/8/31/313 : Laura's patch
2. https://lkml.org/lkml/2014/5/28/64 : Joonsoo's patch

I wanted to allocate the entire ddr chip, in contiguous physical address 0xXXXXXXXX ~ 0xXXXXXXXX
so that the allocation must not be failed.
But it often failed and I found superblocks of some filesystems pined pages for buffer-head.
Therefore I sumbitted a patch, https://lkml.org/lkml/2014/9/4/78.

With them, my platform could've worked for hours
but it still has free-page-counting problem and needs more heavy load test.

Allocation latency Minchan mentioned is not problem for my platform.
CMA allocation is not often and limited to only one drivers.

Allocation guarantee, Minchan menthined, is, my main concern.
I hope it is fixed partly with my patch (https://lkml.org/lkml/2014/9/4/78).

I have a plan to use CMA for massive product next year.
So I'd like to attend LSF/MM and discuss this topic.

Sorry for the wrong request again.

--
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:[~2014-11-30 23: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     ` [Lsf-pc] " Jan Kara
2014-12-01  8:25       ` Joonsoo Kim
2014-11-30 23:54     ` Gioh Kim [this message]
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=547BAE3C.5020309@lge.com \
    --to=gioh.kim@lge.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=jack@suse.cz \
    --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