All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCH v7 7/7] zsmalloc: use shrinker to trigger auto-compaction
Date: Fri, 10 Jul 2015 09:49:21 +0900	[thread overview]
Message-ID: <20150710004921.GA10230@bgram> (raw)
In-Reply-To: <1436355113-12417-8-git-send-email-sergey.senozhatsky@gmail.com>

Hi Sergey,

On Wed, Jul 08, 2015 at 08:31:53PM +0900, Sergey Senozhatsky wrote:
> Perform automatic pool compaction by a shrinker when system
> is getting tight on memory.
> 
> User-space has a very little knowledge regarding zsmalloc fragmentation
> and basically has no mechanism to tell whether compaction will result
> in any memory gain. Another issue is that user space is not always
> aware of the fact that system is getting tight on memory. Which leads
> to very uncomfortable scenarios when user space may start issuing
> compaction 'randomly' or from crontab (for example). Fragmentation
> is not always necessarily bad, allocated and unused objects, after all,
> may be filled with the data later, w/o the need of allocating a new
> zspage. On the other hand, we obviously don't want to waste memory
> when the system needs it.
> 
> Compaction now has a relatively quick pool scan so we are able to
> estimate the number of pages that will be freed easily, which makes it
> possible to call this function from a shrinker->count_objects() callback.
> We also abort compaction as soon as we detect that we can't free any
> pages any more, preventing wasteful objects migrations.
> 
> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> Suggested-by: Minchan Kim <minchan@kernel.org>
Acked-by: Minchan Kim <minchan@kernel.org>

Thanks for great work!

--
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: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCH v7 7/7] zsmalloc: use shrinker to trigger auto-compaction
Date: Fri, 10 Jul 2015 09:49:21 +0900	[thread overview]
Message-ID: <20150710004921.GA10230@bgram> (raw)
In-Reply-To: <1436355113-12417-8-git-send-email-sergey.senozhatsky@gmail.com>

Hi Sergey,

On Wed, Jul 08, 2015 at 08:31:53PM +0900, Sergey Senozhatsky wrote:
> Perform automatic pool compaction by a shrinker when system
> is getting tight on memory.
> 
> User-space has a very little knowledge regarding zsmalloc fragmentation
> and basically has no mechanism to tell whether compaction will result
> in any memory gain. Another issue is that user space is not always
> aware of the fact that system is getting tight on memory. Which leads
> to very uncomfortable scenarios when user space may start issuing
> compaction 'randomly' or from crontab (for example). Fragmentation
> is not always necessarily bad, allocated and unused objects, after all,
> may be filled with the data later, w/o the need of allocating a new
> zspage. On the other hand, we obviously don't want to waste memory
> when the system needs it.
> 
> Compaction now has a relatively quick pool scan so we are able to
> estimate the number of pages that will be freed easily, which makes it
> possible to call this function from a shrinker->count_objects() callback.
> We also abort compaction as soon as we detect that we can't free any
> pages any more, preventing wasteful objects migrations.
> 
> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> Suggested-by: Minchan Kim <minchan@kernel.org>
Acked-by: Minchan Kim <minchan@kernel.org>

Thanks for great work!


  reply	other threads:[~2015-07-10  0:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 11:31 [PATCH v7 0/7] mm/zsmalloc: introduce automatic pool compaction Sergey Senozhatsky
2015-07-08 11:31 ` Sergey Senozhatsky
2015-07-08 11:31 ` [PATCH v7 1/7] zsmalloc: drop unused variable `nr_to_migrate' Sergey Senozhatsky
2015-07-08 11:31   ` Sergey Senozhatsky
2015-07-08 11:31 ` [PATCH v7 2/7] zsmalloc: always keep per-class stats Sergey Senozhatsky
2015-07-08 11:31   ` Sergey Senozhatsky
2015-07-08 11:31 ` [PATCH v7 3/7] zsmalloc: introduce zs_can_compact() function Sergey Senozhatsky
2015-07-08 11:31   ` Sergey Senozhatsky
2015-07-08 11:31 ` [PATCH v7 4/7] zsmalloc: cosmetic compaction code adjustments Sergey Senozhatsky
2015-07-08 11:31   ` Sergey Senozhatsky
2015-07-08 11:31 ` [PATCH v7 5/7] zsmalloc/zram: introduce zs_pool_stats api Sergey Senozhatsky
2015-07-08 11:31   ` Sergey Senozhatsky
2015-07-08 11:31 ` [PATCH v7 6/7] zsmalloc: account the number of compacted pages Sergey Senozhatsky
2015-07-08 11:31   ` Sergey Senozhatsky
2015-07-08 11:31 ` [PATCH v7 7/7] zsmalloc: use shrinker to trigger auto-compaction Sergey Senozhatsky
2015-07-08 11:31   ` Sergey Senozhatsky
2015-07-10  0:49   ` Minchan Kim [this message]
2015-07-10  0:49     ` Minchan Kim
2015-07-10  0:54     ` Sergey Senozhatsky
2015-07-10  0:54       ` Sergey Senozhatsky

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=20150710004921.GA10230@bgram \
    --to=minchan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=sergey.senozhatsky@gmail.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.