All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerome Marchand <jmarchan@redhat.com>
To: Minchan Kim <minchan@kernel.org>, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	juno.choi@lge.com, seungho1.park@lge.com,
	Luigi Semenzato <semenzato@google.com>,
	Nitin Gupta <ngupta@vflare.org>
Subject: Re: [RFC 0/3] zram memory control enhance
Date: Wed, 06 Aug 2014 14:54:28 +0200	[thread overview]
Message-ID: <53E22584.6060900@redhat.com> (raw)
In-Reply-To: <1407225723-23754-1-git-send-email-minchan@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2148 bytes --]

On 08/05/2014 10:02 AM, Minchan Kim wrote:
> Notice! It's RFC. I didn't test at all but wanted to hear opinion
> during merge window when it's really busy time for Andrew so we could
> use the slack time to discuss without hurting him. ;-)
> 
> Patch 1 is to move pages_allocated in zsmalloc from size_class to zs_pool
> so zs_get_total_size_bytes of zsmalloc would be faster than old.
> zs_get_total_size_bytes could be used next patches frequently.
> 
> Patch 2 adds new feature which exports how many of bytes zsmalloc consumes
> during testing workload. Normally, before fixing the zram's disksize
> we have tested various workload and wanted to how many of bytes zram
> consumed.
> For it, we could poll mem_used_total of zram in userspace but the problem is
> when memory pressure is severe and heavy swap out happens suddenly then
> heavy swapin or exist while polling interval of user space is a few second,
> it could miss max memory size zram had consumed easily.
> With lack of information, user can set wrong disksize of zram so the result
> is OOM. So this patch adds max_mem_used for zram and zsmalloc supports it
> 
> Patch 3 is to limit zram memory consumption. Now, zram has no bound for
> memory usage so it could consume up all of system memory. It makes system
> memory control for platform hard so I have heard the feature several time.
> 
> Feedback is welcome!

Hi,

I haven't really reviewed the code yet, but I like the general idea. The
third patch in particular provides a very useful feature. I'm actually
surprised no one provided it earlier.

Jerome


> 
> Minchan Kim (3):
>   zsmalloc: move pages_allocated to zs_pool
>   zsmalloc/zram: add zs_get_max_size_bytes and use it in zram
>   zram: limit memory size for zram
> 
>  Documentation/blockdev/zram.txt |  2 ++
>  drivers/block/zram/zram_drv.c   | 58 +++++++++++++++++++++++++++++++++++++++++
>  drivers/block/zram/zram_drv.h   |  1 +
>  include/linux/zsmalloc.h        |  1 +
>  mm/zsmalloc.c                   | 50 +++++++++++++++++++++++++----------
>  5 files changed, 98 insertions(+), 14 deletions(-)
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 538 bytes --]

  parent reply	other threads:[~2014-08-06 12:54 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05  8:02 [RFC 0/3] zram memory control enhance Minchan Kim
2014-08-05  8:02 ` Minchan Kim
2014-08-05  8:02 ` [RFC 1/3] zsmalloc: move pages_allocated to zs_pool Minchan Kim
2014-08-05  8:02   ` Minchan Kim
2014-08-13 13:59   ` Dan Streetman
2014-08-13 13:59     ` Dan Streetman
2014-08-13 14:14     ` Sergey Senozhatsky
2014-08-13 14:14       ` Sergey Senozhatsky
2014-08-13 14:51       ` Dan Streetman
2014-08-13 14:51         ` Dan Streetman
2014-08-13 15:13         ` Sergey Senozhatsky
2014-08-13 15:13           ` Sergey Senozhatsky
2014-08-13 15:25           ` Sergey Senozhatsky
2014-08-13 15:25             ` Sergey Senozhatsky
2014-08-13 16:11             ` Dan Streetman
2014-08-13 16:11               ` Dan Streetman
2014-08-14 13:03               ` Sergey Senozhatsky
2014-08-14 13:03                 ` Sergey Senozhatsky
2014-08-14  0:09             ` Minchan Kim
2014-08-14  0:09               ` Minchan Kim
2014-08-13 15:21   ` Seth Jennings
2014-08-13 15:21     ` Seth Jennings
2014-08-05  8:02 ` [RFC 2/3] zsmalloc/zram: add zs_get_max_size_bytes and use it in zram Minchan Kim
2014-08-05  8:02   ` Minchan Kim
2014-08-13 15:25   ` Seth Jennings
2014-08-13 15:25     ` Seth Jennings
2014-08-05  8:02 ` [RFC 3/3] zram: limit memory size for zram Minchan Kim
2014-08-05  8:02   ` Minchan Kim
2014-08-05  9:48   ` Minchan Kim
2014-08-05  9:48     ` Minchan Kim
2014-08-05 13:16     ` Sergey Senozhatsky
2014-08-05 13:16       ` Sergey Senozhatsky
2014-08-06  6:52       ` Minchan Kim
2014-08-06  6:52         ` Minchan Kim
2014-08-13 15:30         ` Seth Jennings
2014-08-13 15:30           ` Seth Jennings
2014-08-13 23:31           ` Minchan Kim
2014-08-13 23:31             ` Minchan Kim
2014-08-13 23:27       ` Minchan Kim
2014-08-13 23:27         ` Minchan Kim
2014-08-14 13:29         ` Sergey Senozhatsky
2014-08-14 13:29           ` Sergey Senozhatsky
2014-08-17 23:32           ` Minchan Kim
2014-08-17 23:32             ` Minchan Kim
2014-08-14 14:45         ` Dan Streetman
2014-08-14 14:45           ` Dan Streetman
2014-08-06 12:54 ` Jerome Marchand [this message]
2014-08-13 15:34 ` [RFC 0/3] zram memory control enhance Seth Jennings
2014-08-13 15:34   ` Seth Jennings
2014-08-13 23:32   ` Minchan Kim
2014-08-13 23:32     ` 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=53E22584.6060900@redhat.com \
    --to=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=seungho1.park@lge.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.