From: Petr Cermak <petrcermak@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Primiano Tucci <primiano@chromium.org>,
Petr Cermak <petrcermak@chromium.org>
Subject: [PATCH v2 0/2] task_mmu: Add user-space support for resetting mm->hiwater_rss (peak RSS)
Date: Wed, 7 Jan 2015 17:06:52 +0000 [thread overview]
Message-ID: <cover.1420643264.git.petrcermak@chromium.org> (raw)
Being able to reset mm->hiwater_rss (resident set size high water mark) from
user space would enable fine grained iterative memory profiling. I propose a
very short patch for doing so.
The driving use-case for this would be getting the peak RSS value, which can be
retrieved from the VmHWM field in /proc/pid/status, per benchmark iteration or
test scenario.
Changelog:
v2:
- clarify behaviour in documentation as suggesed by Andrew Morton
<akpm@linux-foundation.org>
- fix a declaration-after-statement warning in fs/proc/task_mmu.c
v1: https://lkml.org/lkml/2014/12/10/312
Petr Cermak (2):
task_mmu: Reduce excessive indentation in clear_refs_write
task_mmu: Add user-space support for resetting mm->hiwater_rss (peak RSS)
Documentation/filesystems/proc.txt | 3 +
fs/proc/task_mmu.c | 115 +++++++++++++++++++++----------------
include/linux/mm.h | 5 ++
3 files changed, 74 insertions(+), 49 deletions(-)
--
2.2.0.rc0.207.ga3a616c
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2015-01-07 17:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 17:06 Petr Cermak [this message]
2015-01-07 17:06 ` [PATCH v2 1/2] task_mmu: Reduce excessive indentation in clear_refs_write Petr Cermak
2015-01-07 17:06 ` [PATCH v2 2/2] task_mmu: Add user-space support for resetting mm->hiwater_rss (peak RSS) Petr Cermak
2015-01-07 17:24 ` Kirill A. Shutemov
2015-01-14 15:22 ` Petr Cermak
2015-01-14 23:36 ` Kirill A. Shutemov
2015-01-21 22:58 ` David Rientjes
2015-01-22 0:22 ` Primiano Tucci
2015-01-22 23:27 ` David Rientjes
2015-01-23 0:28 ` Primiano Tucci
2015-01-27 0:00 ` David Rientjes
2015-02-03 3:26 ` Petr Cermak
2015-02-03 15:51 ` Minchan Kim
2015-02-03 20:16 ` David Rientjes
2015-01-14 23:39 ` Kirill A. Shutemov
2015-01-15 16:46 ` Petr Cermak
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=cover.1420643264.git.petrcermak@chromium.org \
--to=petrcermak@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=primiano@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).