From: Michal Hocko <mhocko@kernel.org>
To: semenzato@chromium.org
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
sonnyrao@chromium.org, Yu Zhao <yuzhao@chromium.org>,
linux-api@vger.kernel.org
Subject: Re: [PATCH v2 1/1] mm: smaps: split PSS into components
Date: Fri, 31 May 2019 08:22:06 +0200 [thread overview]
Message-ID: <20190531062206.GD6896@dhcp22.suse.cz> (raw)
In-Reply-To: <20190531060401.GA7386@dhcp22.suse.cz>
On Fri 31-05-19 08:04:01, Michal Hocko wrote:
> [Please always Cc linux-api mailing list (now added) when adding a new
> user visible API. Keeping the rest of the email intact for reference]
>
> On Thu 30-05-19 17:26:33, semenzato@chromium.org wrote:
> > From: Luigi Semenzato <semenzato@chromium.org>
> >
> > Report separate components (anon, file, and shmem)
> > for PSS in smaps_rollup.
> >
> > This helps understand and tune the memory manager behavior
> > in consumer devices, particularly mobile devices. Many of
> > them (e.g. chromebooks and Android-based devices) use zram
> > for anon memory, and perform disk reads for discarded file
> > pages. The difference in latency is large (e.g. reading
> > a single page from SSD is 30 times slower than decompressing
> > a zram page on one popular device), thus it is useful to know
> > how much of the PSS is anon vs. file.
Could you describe how exactly are those new counters going to be used?
I do not expect this to add a visible penalty to users who are not going
to use the counter but have you tried to measure that?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-05-31 6:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 0:26 [PATCH v2 1/1] mm: smaps: split PSS into components semenzato
2019-05-31 6:04 ` Michal Hocko
2019-05-31 6:22 ` Michal Hocko [this message]
2019-05-31 6:23 ` Michal Hocko
2019-05-31 15:32 ` Luigi Semenzato
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=20190531062206.GD6896@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=semenzato@chromium.org \
--cc=sonnyrao@chromium.org \
--cc=yuzhao@chromium.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;
as well as URLs for NNTP newsgroup(s).