From: Usama Arif <usamaarif642@gmail.com>
To: Suren Baghdasaryan <surenb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>
Cc: Shakeel Butt <shakeel.butt@linux.dev>,
Linux Memory Management List <linux-mm@kvack.org>,
kent.overstreet@linux.dev, vlad.wing@gmail.com
Subject: Re: Memory allocation profiling warnings in memory bound systems
Date: Mon, 19 May 2025 19:31:42 +0100 [thread overview]
Message-ID: <f54f1c91-b778-4082-aa3a-7c2fce46cafc@gmail.com> (raw)
In-Reply-To: <CAJuCfpGLF-RHVwyfdNZ7RKWOvM6H9-tDF7POLgq0fjTPLMP_Hg@mail.gmail.com>
On 19/05/2025 18:56, Suren Baghdasaryan wrote:
> On Mon, May 19, 2025 at 10:29 AM Johannes Weiner <hannes@cmpxchg.org> wrote:
>>
>> On Mon, May 19, 2025 at 06:23:59PM +0100, Usama Arif wrote:
>>> For when the value is inaccurate, it might be better to have the number
>>> and [X] next to it to reflect its inaccurate? Maybe an inaccurate number
>>> is better than no number?
>>
>> Right, it could be a large consumer with only a handful of individual
>> objects missing from the tally due to these extreme corner cases.
>
> Ok, then "<value>?" might make more sense.
Yeah I think that would be good as well.
I guess as long as its loud enough for anyone looking at the profile
to go and have a look at the documentation to see what it would mean.
next prev parent reply other threads:[~2025-05-19 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 13:31 Usama Arif
2025-05-19 13:33 ` Usama Arif
2025-05-19 15:50 ` Suren Baghdasaryan
2025-05-19 16:08 ` Johannes Weiner
2025-05-19 16:42 ` Suren Baghdasaryan
2025-05-19 17:23 ` Usama Arif
2025-05-19 17:29 ` Johannes Weiner
2025-05-19 17:56 ` Suren Baghdasaryan
2025-05-19 18:31 ` Usama Arif [this message]
2025-05-19 18:39 ` Suren Baghdasaryan
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=f54f1c91-b778-4082-aa3a-7c2fce46cafc@gmail.com \
--to=usamaarif642@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-mm@kvack.org \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=vlad.wing@gmail.com \
/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