From: Andrew Morton <akpm@linux-foundation.org>
To: Abhishek Bapat <abhishekbapat@google.com>
Cc: Suren Baghdasaryan <surenb@google.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
Hao Ge <hao.ge@linux.dev>, Shuah Khan <skhan@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Sourav Panda <souravpanda@google.com>
Subject: Re: [PATCH v8 0/6] alloc_tag: introduce IOCTL-based filtering for MAP
Date: Wed, 8 Jul 2026 14:13:41 -0700 [thread overview]
Message-ID: <20260708141341.972033b394dfcc98439b36f9@linux-foundation.org> (raw)
In-Reply-To: <cover.1783532853.git.abhishekbapat@google.com>
On Wed, 8 Jul 2026 18:01:22 +0000 Abhishek Bapat <abhishekbapat@google.com> wrote:
> Currently, memory allocation profiling data is primarily exposed through
> /proc/allocinfo. While useful for manual inspection, this text-based
> interface poses challenges for production monitoring and large-scale
> analysis:
>
> 1. Userspace must parse large amounts of text to extract specific
> fields.
> 2. To find specific tags, userspace must read the entire dataset,
> requiring many context switches and high data copying.
> 3. The kernel currently aggregates per-CPU counters for every allocation
> size, even those the user intends to filter out immediately.
>
> This series introduces a new IOCTL-based binary interface for allocinfo
> that supports kernel-side filtering.
Thanks. The important bits are reviewed, let's get this in there for
some testing.
Sashiko had a lot to say:
https://sashiko.dev/#/patchset/cover.1783532853.git.abhishekbapat@google.com
I think you've already been over this. but please double-check - maybe
it found something new.
prev parent reply other threads:[~2026-07-08 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 18:01 [PATCH v8 0/6] alloc_tag: introduce IOCTL-based filtering for MAP Abhishek Bapat
2026-07-08 18:01 ` [PATCH v8 1/6] alloc_tag: add ioctl to /proc/allocinfo Abhishek Bapat
2026-07-08 18:01 ` [PATCH v8 2/6] alloc_tag: add ioctl filters " Abhishek Bapat
2026-07-08 18:01 ` [PATCH v8 3/6] alloc_tag: add size-based filtering to ioctl Abhishek Bapat
2026-07-08 18:01 ` [PATCH v8 4/6] alloc_tag: add accuracy based " Abhishek Bapat
2026-07-08 18:01 ` [PATCH v8 5/6] kselftest: alloc_tag: add kselftest for ioctl interface Abhishek Bapat
2026-07-09 7:32 ` Hao Ge
2026-07-08 18:01 ` [PATCH v8 6/6] kselftest: alloc_tag: extend the allocinfo ioctl kselftest Abhishek Bapat
2026-07-09 7:47 ` Hao Ge
2026-07-08 21:13 ` Andrew Morton [this message]
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=20260708141341.972033b394dfcc98439b36f9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=abhishekbapat@google.com \
--cc=corbet@lwn.net \
--cc=hao.ge@linux.dev \
--cc=kent.overstreet@linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=skhan@linuxfoundation.org \
--cc=souravpanda@google.com \
--cc=surenb@google.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