mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoyd@nvidia.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	Lorenzo Stoakes <ljs@kernel.org>,
	"Liam R . Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	Shakeel Butt <shakeel.butt@linux.dev>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [RFC PATCH] mm: use precise current RSS for high-water accounting
Date: Thu, 23 Jul 2026 10:07:08 -0700	[thread overview]
Message-ID: <20260723170710.1971749-1-nirmoyd@nvidia.com> (raw)
In-Reply-To: <21d24fc4-141d-4957-8b96-6d5887ef4027@efficios.com>

Hi Mathieu,

On 2026-07-23 12:31, Mathieu Desnoyers wrote:
> What is this test validating ? Does it actually matter for a real-life
> use-case, or is it just the test being too strict ?

It tests getrusage(RUSAGE_CHILDREN).ru_maxrss:

https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/getrusage/getrusage03.c

I am not sure about a real-world use-case; I do not have one.

> What is the overhead impact of your change from approximated counter
> read to a precise sum on this /proc ABI ?

I have not benchmarked the overhead yet. I will get back on this. 

Thanks,
Nirmoy

  reply	other threads:[~2026-07-23 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 13:41 Nirmoy Das
2026-07-23 13:47 ` Mathieu Desnoyers
2026-07-23 16:21   ` Nirmoy Das
2026-07-23 16:31     ` Mathieu Desnoyers
2026-07-23 17:07       ` Nirmoy Das [this message]
2026-07-23 16:58   ` Lorenzo Stoakes (ARM)

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=20260723170710.1971749-1-nirmoyd@nvidia.com \
    --to=nirmoyd@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=shakeel.butt@linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®