From: Marc Dietrich <marvin24@gmx.de>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, 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>,
ds2horner@gmail.com
Subject: Re: [PATCH v2 3/4] zram: zram memory size limitation
Date: Tue, 19 Aug 2014 10:06:22 +0200 [thread overview]
Message-ID: <7959928.Exbvf4HrNB@fb07-iapwap2> (raw)
In-Reply-To: <1408434887-16387-4-git-send-email-minchan@kernel.org>
Am Dienstag, 19. August 2014, 16:54:46 schrieb Minchan Kim:
> 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.
Sorry to jump in late with a probably silly question, but I couldn't find the
answer easily. What's the difference between disksize and mem_limit?
I assume the former is uncompressed size (virtual size) and the latter is
compressed size (real memory usage)? Maybe the difference should be made
clearer in the documentation.
If disksize is the uncompressed size, why would we want to set this at all?
Marc
--
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-19 8:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 7:54 [PATCH v2 0/4] zram memory control enhance Minchan Kim
2014-08-19 7:54 ` [PATCH v2 1/4] zsmalloc: move pages_allocated to zs_pool Minchan Kim
2014-08-19 7:54 ` [PATCH v2 2/4] zsmalloc: change return value unit of zs_get_total_size_bytes Minchan Kim
2014-08-19 14:46 ` Seth Jennings
2014-08-19 15:11 ` Seth Jennings
2014-08-19 23:47 ` Minchan Kim
2014-08-19 23:46 ` Minchan Kim
2014-08-20 4:44 ` Seth Jennings
2014-08-19 7:54 ` [PATCH v2 3/4] zram: zram memory size limitation Minchan Kim
2014-08-19 8:06 ` Marc Dietrich [this message]
2014-08-19 23:32 ` Minchan Kim
2014-08-20 7:58 ` Marc Dietrich
2014-08-19 7:54 ` [PATCH v2 4/4] zram: report maximum used memory Minchan Kim
2014-08-20 6:26 ` David Horner
2014-08-20 6:53 ` Minchan Kim
2014-08-20 7:38 ` David Horner
2014-08-20 7:53 ` Minchan Kim
2014-08-20 8:25 ` David Horner
2014-08-21 0:06 ` 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=7959928.Exbvf4HrNB@fb07-iapwap2 \
--to=marvin24@gmx.de \
--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=minchan@kernel.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