From: Daniel Colascione <dancol@google.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
linux-mm@kvack.org, timmurray@google.com,
linux-kernel@vger.kernel.org, joelaf@google.com
Subject: Re: [PATCH RFC v2] Add /proc/pid/smaps_rollup
Date: Wed, 9 Aug 2017 18:33:44 -0700 [thread overview]
Message-ID: <CAKOZueu3jsD24beRutpATAr3QyxByMv1nJfKT+RRZr83Z+o1qw@mail.gmail.com> (raw)
In-Reply-To: <6d20ced6-a7ca-f4b9-81eb-e34517f97644@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
Thanks for taking a look!
On Aug 9, 2017 6:24 PM, "Randy Dunlap" <rdunlap@infradead.org> wrote:
On 08/09/2017 05:15 PM, Daniel Colascione wrote:
>
> diff --git a/Documentation/ABI/testing/procfs-smaps_rollup
b/Documentation/ABI/testing/procfs-smaps_rollup
> new file mode 100644
> index 000000000000..fd5a3699edf1
> --- /dev/null
> +++ b/Documentation/ABI/testing/procfs-smaps_rollup
> @@ -0,0 +1,34 @@
> +What: /proc/pid/smaps_Rollup
smaps_rollup
Gah. Thanks.
\although I would prefer smaps_summary. whatever.
I'm open to anything.
[-- Attachment #2: Type: text/html, Size: 1455 bytes --]
next prev parent reply other threads:[~2017-08-10 1:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170808132554.141143-1-dancol@google.com>
2017-08-08 18:22 ` [PATCH] Add /proc/pid/smaps_rollup Daniel Colascione
2017-08-08 18:42 ` Greg KH
2017-08-08 18:51 ` Daniel Colascione
2017-08-08 18:56 ` Greg KH
2017-08-10 0:15 ` [PATCH RFC v2] " Daniel Colascione
2017-08-10 1:24 ` Randy Dunlap
2017-08-10 1:33 ` Daniel Colascione [this message]
2017-08-10 4:38 ` Minchan Kim
2017-08-10 8:46 ` Michal Hocko
2017-08-10 10:23 ` Daniel Colascione
2017-08-10 10:58 ` Michal Hocko
2017-08-10 18:56 ` Sonny Rao
2017-08-10 19:17 ` Tim Murray
2017-08-24 8:55 ` Michal Hocko
2017-08-25 21:16 ` Andrew Morton
2017-08-28 11:30 ` Michal Hocko
2017-08-12 2:21 ` [PATCH v3] " Daniel Colascione
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=CAKOZueu3jsD24beRutpATAr3QyxByMv1nJfKT+RRZr83Z+o1qw@mail.gmail.com \
--to=dancol@google.com \
--cc=joelaf@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=timmurray@google.com \
--cc=viro@zeniv.linux.org.uk \
/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).