Re: [PATCH v3 0/6] alloc_tag: introduce IOCTL-based filtering for MAP

[Abhishek Bapat]

On Fri, Jun 5, 2026 at 5:09 PM Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> On Fri,  5 Jun 2026 23:36:45 +0000 Abhishek Bapat <abhishekbapat@xxxxxxxxxx> 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. By allowing the user to specify a
> > filter mask, we significantly reduce the work performed in-kernel and
> > the amount of data transferred to userspace.
>
> Thanks.  AI review found several things - you'll want to address at
> least the first few.
>
>         https://sashiko.dev/#/patchset/cover.1780701922.git.abhishekbapat@xxxxxxxxxx

All, please note I missed attaching the reason for choosing the IOCTL
mechanism to this cover letter, but I will attach it to the v4
patchset cover letter along with other changes. Thanks!