[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJuCfpEGpLJMTDS30Z0xpurbxtRS2LKx1G2=u=kPknpBrHK6jA@mail.gmail.com>
Date: Tue, 16 Sep 2025 09:02:22 -0700
From: Suren Baghdasaryan <surenb@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: kent.overstreet@...ux.dev, vbabka@...e.cz, hannes@...xchg.org,
usamaarif642@...il.com, rientjes@...gle.com, roman.gushchin@...ux.dev,
harry.yoo@...cle.com, shakeel.butt@...ux.dev, 00107082@....com,
pyyjason@...il.com, pasha.tatashin@...een.com, souravpanda@...gle.com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/1] alloc_tag: mark inaccurate allocation counters in
/proc/allocinfo output
On Mon, Sep 15, 2025 at 9:39 PM Suren Baghdasaryan <surenb@...gle.com> wrote:
>
> On Mon, Sep 15, 2025 at 9:21 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
> >
> > On Mon, 15 Sep 2025 20:34:33 -0700 Suren Baghdasaryan <surenb@...gle.com> wrote:
> >
> > > >
> > > > > could you fold it into the existing patch or
> > > > > should I respin?
> > > >
> > > > A little fixlet would be preferred (by me, at least).
> > >
> > > Ok, should I post a fixup patch or you will do that in-place?
> >
> > I think the former, please. Your intent is preferable to my
> > interpretation of your intent and we get all the nice patch metadata to
> > track everything.
>
> Will do first thing in the morning. Thanks!
Posted at: https://lore.kernel.org/all/20250916160110.266190-1-surenb@google.com/
>
> >
Powered by blists - more mailing lists