[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150511113833.GO27969@ws.net.home>
Date: Mon, 11 May 2015 13:38:33 +0200
From: Karel Zak <kzak@...hat.com>
To: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc: Minchan Kim <minchan@...nel.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
linux-kernel@...r.kernel.org, util-linux@...r.kernel.org
Subject: Re: what's cooking in zram for 4.1
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.
Thanks.
> 2) zram has deprecated some of the existing stat sysfs attributes. we will
> consolidate zramX device's stats in 3 files, rather than having N files (per-stat).
sysfs attributes used by zramctl(8) are:
disksize
orig_data_size
compr_data_size
comp_algorithm
max_comp_streams
mem_used_total
reset
> -- /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:
hmm... frankly, the reason why I love /sys and why hate /proc is
value-per-file. You do not need special parsers to read from /sys
(usually).
> orig_data_size
> compr_data_size
> mem_used_total
> mem_limit
> mem_used_max
> zero_pages
> num_migrated
Why do you need all in one file? ... to provide consistent statistics?
Karel
--
Karel Zak <kzak@...hat.com>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists