From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Karel Zak <kzak@redhat.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
linux-kernel@vger.kernel.org, util-linux@vger.kernel.org
Subject: Re: what's cooking in zram for 4.1
Date: Mon, 18 May 2015 18:56:49 +0900 [thread overview]
Message-ID: <20150518095649.GB2330@swordfish> (raw)
In-Reply-To: <20150518093645.GL4834@ws.net.home>
On (05/18/15 11:36), Karel Zak wrote:
> On Sat, May 09, 2015 at 01:21:48PM +0900, Sergey Senozhatsky wrote:
> > There will be some user-space visible changes in zram 4.1 we'd love to let you know
> > about.
>
> ...
>
> > -- /sys/block/zram<id>/mm_stat
> >
> > The stat file represents device's mm statistics. It consists of a single
> > line of text and contains the following stats separated by whitespace:
> > orig_data_size
> > compr_data_size
> > mem_used_total
> > mem_limit
> > mem_used_max
> > zero_pages
> > num_migrated
>
> OK, zramctl(8) code in util-linux git tree supports mm_stat file now.
> It's able to fallback to the original /sys/block/zram<id>/<attr> if
> mm_stat does not exist. The change will be available in v2.27 (~Aug 2015).
>
> I have also added support for MEM-LIMIT, MEM-USED and MIGRATED columns.
>
great, thanks!
-ss
next prev parent reply other threads:[~2015-05-18 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 4:21 what's cooking in zram for 4.1 Sergey Senozhatsky
2015-05-11 11:38 ` Karel Zak
2015-05-11 11:56 ` Sergey Senozhatsky
2015-05-18 13:55 ` Minchan Kim
2015-05-18 14:40 ` Sergey Senozhatsky
2015-05-18 9:36 ` Karel Zak
2015-05-18 9:56 ` Sergey Senozhatsky [this message]
2015-05-18 13:56 ` 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=20150518095649.GB2330@swordfish \
--to=sergey.senozhatsky.work@gmail.com \
--cc=kzak@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=util-linux@vger.kernel.org \
/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