All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Rik van Riel <riel@redhat.com>, Minchan Kim <minchan@kernel.org>,
	Redmond <u93410091@gmail.com>,
	"ZhaoJunmin Zhao(Junmin)" <zhaojunmin@huawei.com>,
	Vinayak Menon <vinmenon@codeaurora.org>,
	Juneho Choi <juno.choi@lge.com>,
	Sangwoo Park <sangwoo2.park@lge.com>,
	Chan Gyun Jeong <chan.jeong@lge.com>
Subject: [PATCH v1 0/3] per-process reclaim
Date: Mon, 13 Jun 2016 16:50:55 +0900	[thread overview]
Message-ID: <1465804259-29345-1-git-send-email-minchan@kernel.org> (raw)

Hi all,

http://thread.gmane.org/gmane.linux.kernel/1480728

I sent per-process reclaim patchset three years ago. Then, last
feedback from akpm was that he want to know real usecase scenario.

Since then, I got question from several embedded people of various
company "why it's not merged into mainline" and heard they have used
the feature as in-house patch and recenlty, I noticed android from
Qualcomm started to use it.

Of course, our product have used it and released it in real procuct.

Quote from Sangwoo Park <angwoo2.park@lge.com>
Thanks for the data, Sangwoo!
"
- Test scenaro
  - platform: android
  - target: MSM8952, 2G DDR, 16G eMMC
  - scenario
    retry app launch and Back Home with 16 apps and 16 turns
    (total app launch count is 256)
  - result:
			  resume count   |  cold launching count
-----------------------------------------------------------------
 vanilla           |           85        |          171
 perproc reclaim   |           184       |           72
"

Higher resume count is better because cold launching needs loading
lots of resource data which takes above 15 ~ 20 seconds for some
games while successful resume just takes 1~5 second.

As perproc reclaim way with new management policy, we could reduce
cold launching a lot(i.e., 171-72) so that it reduces app startup
a lot.

Another useful function from this feature is to make swapout easily
which is useful for testing swapout stress and workloads.

Thanks.

Cc: Redmond <u93410091@gmail.com>
Cc: ZhaoJunmin Zhao(Junmin) <zhaojunmin@huawei.com>
Cc: Vinayak Menon <vinmenon@codeaurora.org>
Cc: Juneho Choi <juno.choi@lge.com>
Cc: Sangwoo Park <sangwoo2.park@lge.com>
Cc: Chan Gyun Jeong <chan.jeong@lge.com>

Minchan Kim (3):
  mm: vmscan: refactoring force_reclaim
  mm: vmscan: shrink_page_list with multiple zones
  mm: per-process reclaim

 Documentation/filesystems/proc.txt |  15 ++++
 fs/proc/base.c                     |   1 +
 fs/proc/internal.h                 |   1 +
 fs/proc/task_mmu.c                 | 149 +++++++++++++++++++++++++++++++++++++
 include/linux/rmap.h               |   4 +
 mm/vmscan.c                        |  85 ++++++++++++++++-----
 6 files changed, 235 insertions(+), 20 deletions(-)

-- 
1.9.1

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

WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Rik van Riel <riel@redhat.com>, Minchan Kim <minchan@kernel.org>,
	Redmond <u93410091@gmail.com>,
	"ZhaoJunmin Zhao(Junmin)" <zhaojunmin@huawei.com>,
	Vinayak Menon <vinmenon@codeaurora.org>,
	Juneho Choi <juno.choi@lge.com>,
	Sangwoo Park <sangwoo2.park@lge.com>,
	Chan Gyun Jeong <chan.jeong@lge.com>
Subject: [PATCH v1 0/3] per-process reclaim
Date: Mon, 13 Jun 2016 16:50:55 +0900	[thread overview]
Message-ID: <1465804259-29345-1-git-send-email-minchan@kernel.org> (raw)

Hi all,

http://thread.gmane.org/gmane.linux.kernel/1480728

I sent per-process reclaim patchset three years ago. Then, last
feedback from akpm was that he want to know real usecase scenario.

Since then, I got question from several embedded people of various
company "why it's not merged into mainline" and heard they have used
the feature as in-house patch and recenlty, I noticed android from
Qualcomm started to use it.

Of course, our product have used it and released it in real procuct.

Quote from Sangwoo Park <angwoo2.park@lge.com>
Thanks for the data, Sangwoo!
"
- Test scenaro
  - platform: android
  - target: MSM8952, 2G DDR, 16G eMMC
  - scenario
    retry app launch and Back Home with 16 apps and 16 turns
    (total app launch count is 256)
  - result:
			  resume count   |  cold launching count
-----------------------------------------------------------------
 vanilla           |           85        |          171
 perproc reclaim   |           184       |           72
"

Higher resume count is better because cold launching needs loading
lots of resource data which takes above 15 ~ 20 seconds for some
games while successful resume just takes 1~5 second.

As perproc reclaim way with new management policy, we could reduce
cold launching a lot(i.e., 171-72) so that it reduces app startup
a lot.

Another useful function from this feature is to make swapout easily
which is useful for testing swapout stress and workloads.

Thanks.

Cc: Redmond <u93410091@gmail.com>
Cc: ZhaoJunmin Zhao(Junmin) <zhaojunmin@huawei.com>
Cc: Vinayak Menon <vinmenon@codeaurora.org>
Cc: Juneho Choi <juno.choi@lge.com>
Cc: Sangwoo Park <sangwoo2.park@lge.com>
Cc: Chan Gyun Jeong <chan.jeong@lge.com>

Minchan Kim (3):
  mm: vmscan: refactoring force_reclaim
  mm: vmscan: shrink_page_list with multiple zones
  mm: per-process reclaim

 Documentation/filesystems/proc.txt |  15 ++++
 fs/proc/base.c                     |   1 +
 fs/proc/internal.h                 |   1 +
 fs/proc/task_mmu.c                 | 149 +++++++++++++++++++++++++++++++++++++
 include/linux/rmap.h               |   4 +
 mm/vmscan.c                        |  85 ++++++++++++++++-----
 6 files changed, 235 insertions(+), 20 deletions(-)

-- 
1.9.1

             reply	other threads:[~2016-06-13  7:51 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13  7:50 Minchan Kim [this message]
2016-06-13  7:50 ` [PATCH v1 0/3] per-process reclaim Minchan Kim
2016-06-13  7:50 ` [PATCH v1 1/3] mm: vmscan: refactoring force_reclaim Minchan Kim
2016-06-13  7:50   ` Minchan Kim
2016-06-13  7:50 ` [PATCH v1 2/3] mm: vmscan: shrink_page_list with multiple zones Minchan Kim
2016-06-13  7:50   ` Minchan Kim
2016-06-13  7:50 ` [PATCH v1 3/3] mm: per-process reclaim Minchan Kim
2016-06-13  7:50   ` Minchan Kim
2016-06-13 15:06   ` Johannes Weiner
2016-06-13 15:06     ` Johannes Weiner
2016-06-15  0:40     ` Minchan Kim
2016-06-15  0:40       ` Minchan Kim
2016-06-16 11:07       ` Michal Hocko
2016-06-16 11:07         ` Michal Hocko
2016-06-16 14:41       ` Johannes Weiner
2016-06-16 14:41         ` Johannes Weiner
2016-06-17  6:43         ` Minchan Kim
2016-06-17  6:43           ` Minchan Kim
2016-06-17  7:24     ` Balbir Singh
2016-06-17  7:24       ` Balbir Singh
2016-06-17  7:57       ` Vinayak Menon
2016-06-17  7:57         ` Vinayak Menon
2016-06-13 17:06   ` Rik van Riel
2016-06-15  1:01     ` Minchan Kim
2016-06-15  1:01       ` Minchan Kim
2016-06-13 11:50 ` [PATCH v1 0/3] " Chen Feng
2016-06-13 11:50   ` Chen Feng
2016-06-13 12:22   ` ZhaoJunmin Zhao(Junmin)
2016-06-13 12:22     ` ZhaoJunmin Zhao(Junmin)
2016-06-15  0:43   ` Minchan Kim
2016-06-15  0:43     ` Minchan Kim
2016-06-13 13:29 ` Vinayak Menon
2016-06-13 13:29   ` Vinayak Menon
2016-06-15  0:57   ` Minchan Kim
2016-06-15  0:57     ` Minchan Kim
2016-06-16  4:21     ` Vinayak Menon
2016-06-16  4:21       ` Vinayak Menon

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=1465804259-29345-1-git-send-email-minchan@kernel.org \
    --to=minchan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=chan.jeong@lge.com \
    --cc=juno.choi@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@redhat.com \
    --cc=sangwoo2.park@lge.com \
    --cc=u93410091@gmail.com \
    --cc=vinmenon@codeaurora.org \
    --cc=zhaojunmin@huawei.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 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.