From: Minchan Kim <minchan@kernel.org>
To: Dongsheng Song <dongsheng.song@gmail.com>
Cc: David Horner <ds2horner@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
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>
Subject: Re: [PATCH v4 3/4] zram: zram memory size limitation
Date: Tue, 26 Aug 2014 13:51:00 +0900 [thread overview]
Message-ID: <20140826045100.GD11319@bbox> (raw)
In-Reply-To: <CAE8XmWojKVaaY2GzRnpOVzc9cMeX2fb3nRC0JyBgrhPu1QaBEw@mail.gmail.com>
Hello,
On Mon, Aug 25, 2014 at 04:25:31PM +0800, Dongsheng Song wrote:
> > +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.
>
> extra word 'store' ?
> The mem_limit file is read/write and specifies the amount of memory to
> be able to consume memory to store store compressed data.
>
> maybe this better ?
> The mem_limit file is read/write and specifies the amount of memory to
> store compressed data.
Will fix.
Thanks!
>
> --
> Dongsheng
>
> --
> 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>
--
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:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 0:42 [PATCH v4 0/4] zram memory control enhance Minchan Kim
2014-08-22 0:42 ` [PATCH v4 1/4] zsmalloc: move pages_allocated to zs_pool Minchan Kim
2014-08-22 0:42 ` [PATCH v4 2/4] zsmalloc: change return value unit of zs_get_total_size_bytes Minchan Kim
2014-08-22 0:42 ` [PATCH v4 3/4] zram: zram memory size limitation Minchan Kim
2014-08-22 10:55 ` David Horner
2014-08-22 18:47 ` Dan Streetman
2014-08-24 23:56 ` Minchan Kim
2014-08-25 3:40 ` David Horner
2014-08-25 4:37 ` Minchan Kim
2014-08-25 8:22 ` David Horner
2014-08-25 18:12 ` Dan Streetman
2014-08-26 1:54 ` David Horner
2014-08-26 4:39 ` Minchan Kim
2014-08-26 5:36 ` David Horner
2014-08-26 13:31 ` Dan Streetman
2014-08-26 4:28 ` David Horner
2014-08-26 13:40 ` Dan Streetman
2014-08-25 8:25 ` Dongsheng Song
2014-08-26 4:51 ` Minchan Kim [this message]
2014-08-22 0:42 ` [PATCH v4 4/4] zram: report maximum used memory Minchan Kim
2014-08-22 19:15 ` [PATCH v4 0/4] zram memory control enhance Dan Streetman
2014-08-24 23:58 ` 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=20140826045100.GD11319@bbox \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ddstreet@ieee.org \
--cc=dongsheng.song@gmail.com \
--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).