From: "\"박승호/책임연구원/SW Platform(연)AOT팀(seungho1.park@lge.com)\"" <seungho1.park@lge.com>
To: Minchan Kim <minchan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Nitin Gupta <ngupta@vflare.org>,
Dan Streetman <ddstreet@ieee.org>,
Seth Jennings <sjennings@variantweb.net>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Luigi Semenzato <semenzato@google.com>,
Jerome Marchand <jmarchan@redhat.com>,
juno.choi@lge.com
Subject: Re: [RFC 0/6] zsmalloc support compaction
Date: Thu, 04 Dec 2014 15:49:21 +0900 [thread overview]
Message-ID: <548003F1.2080004@lge.com> (raw)
In-Reply-To: <1417488587-28609-1-git-send-email-minchan@kernel.org>
Hi, Minchan.
I have a question.
The problem mentioned can't be resolved with compaction?
Is there any reason that zsmalloc pages can't be moved by compaction
operation in direct reclaim?
2014-12-02 i??i ? 11:49i?? Minchan Kim i?'(e??) i?' e,?:
> Recently, there was issue about zsmalloc fragmentation and
> I got a report from Juno that new fork failed although there
> are plenty of free pages in the system.
> His investigation revealed zram is one of the culprit to make
> heavy fragmentation so there was no more contiguous 16K page
> for pgd to fork in the ARM.
>
> This patchset implement *basic* zsmalloc compaction support
> and zram utilizes it so admin can do
> "echo 1 > /sys/block/zram0/compact"
>
> Actually, ideal is that mm migrate code is aware of zram pages and
> migrate them out automatically without admin's manual opeartion
> when system is out of contiguous page. Howver, we need more thinking
> before adding more hooks to migrate.c. Even though we implement it,
> we need manual trigger mode, too so I hope we could enhance
> zram migration stuff based on this primitive functions in future.
>
> I just tested it on only x86 so need more testing on other arches.
> Additionally, I should have a number for zsmalloc regression
> caused by indirect layering. Unfortunately, I don't have any
> ARM test machine on my desk. I will get it soon and test it.
> Anyway, before further work, I'd like to hear opinion.
>
> Pathset is based on v3.18-rc6-mmotm-2014-11-26-15-45.
>
> Thanks.
>
> Minchan Kim (6):
> zsmalloc: expand size class to support sizeof(unsigned long)
> zsmalloc: add indrection layer to decouple handle from object
> zsmalloc: implement reverse mapping
> zsmalloc: encode alloced mark in handle object
> zsmalloc: support compaction
> zram: support compaction
>
> drivers/block/zram/zram_drv.c | 24 ++
> drivers/block/zram/zram_drv.h | 1 +
> include/linux/zsmalloc.h | 1 +
> mm/zsmalloc.c | 596 +++++++++++++++++++++++++++++++++++++-----
> 4 files changed, 552 insertions(+), 70 deletions(-)
>
--
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-12-04 6:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 2:49 [RFC 0/6] zsmalloc support compaction Minchan Kim
2014-12-02 2:49 ` [RFC 1/6] zsmalloc: expand size class to support sizeof(unsigned long) Minchan Kim
2014-12-02 2:49 ` [RFC 2/6] zsmalloc: add indrection layer to decouple handle from object Minchan Kim
2014-12-02 2:49 ` [RFC 3/6] zsmalloc: implement reverse mapping Minchan Kim
2014-12-02 2:49 ` [RFC 4/6] zsmalloc: encode alloced mark in handle object Minchan Kim
2014-12-02 2:49 ` [RFC 5/6] zsmalloc: support compaction Minchan Kim
2014-12-02 2:49 ` [RFC 6/6] zram: " Minchan Kim
2014-12-04 6:49 ` "박승호/책임연구원/SW Platform(연)AOT팀(seungho1.park@lge.com)" [this message]
2014-12-04 7:20 ` [RFC 0/6] zsmalloc " Minchan Kim
2014-12-04 7:29 ` "박승호/책임연구원/SW Platform(연)AOT팀(seungho1.park@lge.com)"
2014-12-04 7:21 ` "박승호/책임연구원/SW Platform(연)AOT팀(seungho1.park@lge.com)"
2014-12-17 23:19 ` Seth Jennings
2014-12-18 1:50 ` Ganesh Mahendran
2014-12-19 0:46 ` Minchan Kim
2014-12-23 2:50 ` Minchan Kim
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=548003F1.2080004@lge.com \
--to=seungho1.park@lge.com \
--cc=akpm@linux-foundation.org \
--cc=ddstreet@ieee.org \
--cc=jmarchan@redhat.com \
--cc=juno.choi@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=semenzato@google.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=sjennings@variantweb.net \
/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).