From: Vlastimil Babka <vbabka@suse.cz>
To: Suren Baghdasaryan <surenb@google.com>,
Usama Arif <usamaarif642@gmail.com>
Cc: akpm@linux-foundation.org, kent.overstreet@linux.dev,
hannes@cmpxchg.org, rientjes@google.com,
roman.gushchin@linux.dev, harry.yoo@oracle.com,
shakeel.butt@linux.dev, 00107082@163.com, pyyjason@gmail.com,
pasha.tatashin@soleen.com, souravpanda@google.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] alloc_tag: mark inaccurate allocation counters in /proc/allocinfo output
Date: Wed, 17 Sep 2025 09:38:43 +0200 [thread overview]
Message-ID: <af62a2c2-3c01-408d-b694-aa7e95d23c18@suse.cz> (raw)
In-Reply-To: <CAJuCfpEULVxMixDjrk_xg7+3+97dkcMmkDd++BaR17X4tDSs6Q@mail.gmail.com>
On 9/17/25 00:26, Suren Baghdasaryan wrote:
> On Tue, Sep 16, 2025 at 9:52 PM Usama Arif <usamaarif642@gmail.com> wrote:
>
> Hmm. Missing a large allocation and not knowing about it can be a problem...
> I'll start sketching a patch to see if tracking such a global counter
> has any drawbacks and in the meantime I'm open to suggestions on how
> to expose it to the userspace.
Could it be made to look like an actual tag in the output?
e.g. lib/alloc_tag.c:1234 func:untracked_slab_objects
(probably some better name conveying it's uknown due to failure to allocate
objexts)
Maybe even implemented in a way that it's not a specially crafted output line.
> About concerns on the IOCTL interface, would it be more usable if we
> get the alloctop [1] or a similar tool which can be used to easily
> issue such commands into kernel/tools?
>
> [1] https://android-review.git.corp.google.com/c/platform/system/memory/libmeminfo/+/3431860
>
>>
next prev parent reply other threads:[~2025-09-17 7:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 23:02 Suren Baghdasaryan
2025-09-15 23:05 ` Suren Baghdasaryan
2025-09-16 0:11 ` Andrew Morton
2025-09-16 2:48 ` Suren Baghdasaryan
2025-09-16 2:56 ` Andrew Morton
2025-09-16 3:34 ` Suren Baghdasaryan
2025-09-16 4:21 ` Andrew Morton
2025-09-16 4:39 ` Suren Baghdasaryan
2025-09-16 16:02 ` Suren Baghdasaryan
2025-09-16 12:57 ` Vlastimil Babka
2025-09-16 15:51 ` Suren Baghdasaryan
2025-09-16 21:11 ` Usama Arif
2025-09-16 21:46 ` Suren Baghdasaryan
2025-09-16 21:52 ` Usama Arif
2025-09-16 22:26 ` Suren Baghdasaryan
2025-09-16 22:27 ` Suren Baghdasaryan
2025-09-17 21:09 ` Usama Arif
2025-09-17 23:04 ` Suren Baghdasaryan
2025-09-17 7:38 ` Vlastimil Babka [this message]
2025-09-17 23:02 ` 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=af62a2c2-3c01-408d-b694-aa7e95d23c18@suse.cz \
--to=vbabka@suse.cz \
--cc=00107082@163.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=harry.yoo@oracle.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pyyjason@gmail.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=souravpanda@google.com \
--cc=surenb@google.com \
--cc=usamaarif642@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