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,
Jerome Marchand <jmarchan@redhat.com>,
juno.choi@lge.com, seungho1.park@lge.com,
Luigi Semenzato <semenzato@google.com>,
Nitin Gupta <ngupta@vflare.org>,
Seth Jennings <sjennings@variantweb.net>,
Dan Streetman <ddstreet@ieee.org>,
ds2horner@gmail.com
Subject: Re: [PATCH v5 3/4] zram: zram memory size limitation
Date: Tue, 26 Aug 2014 13:52:14 +0900 [thread overview]
Message-ID: <20140826045214.GE11319@bbox> (raw)
In-Reply-To: <20140825110927.GB933@swordfish>
Hey Sergey,
On Mon, Aug 25, 2014 at 08:09:27PM +0900, Sergey Senozhatsky wrote:
> On (08/25/14 09:05), Minchan Kim wrote:
> > Since zram has no control feature to limit memory usage,
> > it makes hard to manage system memrory.
> >
> > This patch adds new knob "mem_limit" via sysfs to set up the
> > a limit so that zram could fail allocation once it reaches
> > the limit.
> >
> > In addition, user could change the limit in runtime so that
> > he could manage the memory more dynamically.
> >
> > Initial state is no limit so it doesn't break old behavior.
> >
> > Signed-off-by: Minchan Kim <minchan@kernel.org>
> > ---
> > Documentation/ABI/testing/sysfs-block-zram | 10 ++++++++
> > Documentation/blockdev/zram.txt | 24 ++++++++++++++---
> > drivers/block/zram/zram_drv.c | 41 ++++++++++++++++++++++++++++++
> > drivers/block/zram/zram_drv.h | 5 ++++
> > 4 files changed, 76 insertions(+), 4 deletions(-)
> >
> > diff --git a/Documentation/ABI/testing/sysfs-block-zram b/Documentation/ABI/testing/sysfs-block-zram
> > index 70ec992514d0..dbe643775ec1 100644
> > --- a/Documentation/ABI/testing/sysfs-block-zram
> > +++ b/Documentation/ABI/testing/sysfs-block-zram
> > @@ -119,3 +119,13 @@ Description:
> > efficiency can be calculated using compr_data_size and this
> > statistic.
> > Unit: bytes
> > +
> > +What: /sys/block/zram<id>/mem_limit
> > +Date: August 2014
> > +Contact: Minchan Kim <minchan@kernel.org>
> > +Description:
> > + The mem_limit file is read/write and specifies the amount
> > + of memory to be able to consume memory to store store
> > + compressed data. The limit could be changed in run time
> > + and "0" means disable the limit. No limit is the initial state.
>
> just a nitpick, sorry.
> "the amount of memory to be able to consume memory to store store compressed data"
> ^^^^^^^
>
> "the maximum amount of memory ZRAM can use to store the compressed data"?
Will fix.
Thanks.
--
Kind regards,
Minchan Kim
--
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-08-26 4:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 0:05 [PATCH v5 0/4] zram memory control enhance Minchan Kim
2014-08-25 0:05 ` [PATCH v5 1/4] zsmalloc: move pages_allocated to zs_pool Minchan Kim
2014-08-25 0:05 ` [PATCH v5 2/4] zsmalloc: change return value unit of zs_get_total_size_bytes Minchan Kim
2014-08-25 4:08 ` David Horner
2014-08-25 0:05 ` [PATCH v5 3/4] zram: zram memory size limitation Minchan Kim
2014-08-25 11:09 ` Sergey Senozhatsky
2014-08-26 4:52 ` Minchan Kim [this message]
2014-08-26 7:37 ` Joonsoo Kim
2014-08-26 7:55 ` Minchan Kim
2014-08-26 12:22 ` David Horner
2014-08-27 1:26 ` Joonsoo Kim
2014-08-27 2:51 ` Minchan Kim
2014-08-27 5:04 ` Joonsoo Kim
2014-08-27 7:28 ` Minchan Kim
2014-08-28 8:21 ` Joonsoo Kim
2014-08-27 14:03 ` Dan Streetman
2014-08-27 14:44 ` David Horner
2014-08-27 15:14 ` Dan Streetman
2014-08-27 15:35 ` David Horner
2014-08-27 16:29 ` Dan Streetman
2014-08-27 16:59 ` David Horner
2014-08-27 19:04 ` Dan Streetman
2014-08-28 3:04 ` Minchan Kim
2014-08-28 2:59 ` Minchan Kim
2014-08-28 2:52 ` Minchan Kim
2014-08-25 0:05 ` [PATCH v5 4/4] zram: report maximum used memory Minchan Kim
2014-08-25 4:05 ` David Horner
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=20140826045214.GE11319@bbox \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ddstreet@ieee.org \
--cc=ds2horner@gmail.com \
--cc=jmarchan@redhat.com \
--cc=juno.choi@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ngupta@vflare.org \
--cc=semenzato@google.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=seungho1.park@lge.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).