From: Sergey Senozhatsky <sergey.senozhatsky@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, 11 May 2015 20:56:02 +0900 [thread overview]
Message-ID: <20150511115602.GA483@swordfish> (raw)
In-Reply-To: <20150511113833.GO27969@ws.net.home>
On (05/11/15 13:38), Karel Zak wrote:
> 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?
>
yes, that's the main reason.
-ss
next prev parent reply other threads:[~2015-05-11 11: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 [this message]
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
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=20150511115602.GA483@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=kzak@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky.work@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.