From: Minchan Kim <minchan@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: linux-mm@kvack.org, Jerome Marchand <jmarchan@redhat.com>,
linux-kernel@vger.kernel.org, juno.choi@lge.com,
seungho1.park@lge.com, Luigi Semenzato <semenzato@google.com>,
Nitin Gupta <ngupta@vflare.org>
Subject: Re: [RFC 3/3] zram: limit memory size for zram
Date: Wed, 6 Aug 2014 15:52:53 +0900 [thread overview]
Message-ID: <20140806065253.GC3796@bbox> (raw)
In-Reply-To: <20140805131615.GA961@swordfish>
On Tue, Aug 05, 2014 at 10:16:15PM +0900, Sergey Senozhatsky wrote:
> Hello,
>
> On (08/05/14 18:48), Minchan Kim wrote:
> > Another idea: we could define void zs_limit_mem(unsinged long nr_pages)
> > in zsmalloc and put the limit in zs_pool via new API from zram so that
> > zs_malloc could be failed as soon as it exceeds the limit.
> >
> > In the end, zram doesn't need to call zs_get_total_size_bytes on every
> > write. It's more clean and right layer, IMHO.
>
> yes, I think this one is better.
>
> -ss
next prev parent reply other threads:[~2014-08-06 6:52 UTC|newest]
Thread overview: 26+ 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 ` [RFC 1/3] zsmalloc: move pages_allocated to zs_pool Minchan Kim
2014-08-13 13:59 ` Dan Streetman
2014-08-13 14:14 ` Sergey Senozhatsky
2014-08-13 14:51 ` Dan Streetman
2014-08-13 15:13 ` Sergey Senozhatsky
2014-08-13 15:25 ` Sergey Senozhatsky
2014-08-13 16:11 ` Dan Streetman
2014-08-14 13:03 ` Sergey Senozhatsky
2014-08-14 0:09 ` Minchan Kim
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-13 15:25 ` Seth Jennings
2014-08-05 8:02 ` [RFC 3/3] zram: limit memory size for zram Minchan Kim
2014-08-05 9:48 ` Minchan Kim
2014-08-05 13:16 ` Sergey Senozhatsky
2014-08-06 6:52 ` Minchan Kim [this message]
2014-08-13 15:30 ` Seth Jennings
2014-08-13 23:31 ` Minchan Kim
2014-08-13 23:27 ` Minchan Kim
2014-08-14 13:29 ` Sergey Senozhatsky
2014-08-17 23:32 ` Minchan Kim
2014-08-14 14:45 ` Dan Streetman
2014-08-06 12:54 ` [RFC 0/3] zram memory control enhance Jerome Marchand
2014-08-13 15:34 ` Seth Jennings
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=20140806065253.GC3796@bbox \
--to=minchan@kernel.org \
--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 \
/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).