[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8427ebb5-61d0-f0ad-3bfa-6aaf575427e4@suse.cz>
Date: Mon, 12 Jun 2023 11:44:39 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Andrew Morton <akpm@...ux-foundation.org>,
Oscar Salvador <osalvador@...e.de>
Cc: Alexander Potapenko <glider@...gle.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Michal Hocko <mhocko@...e.com>,
Eric Dumazet <edumazet@...gle.com>,
Waiman Long <longman@...hat.com>,
Suren Baghdasaryan <surenb@...gle.com>,
Marco Elver <elver@...gle.com>,
Andrey Konovalov <andreyknvl@...il.com>
Subject: Re: [PATCH v4 0/3] page_owner: print stacks and their counter
On 6/9/23 23:55, Andrew Morton wrote:
> On Mon, 24 Apr 2023 05:54:59 +0200 Oscar Salvador <osalvador@...e.de> wrote:
>
>> > Given that no other stackdepot user needs these counters, maybe it
>> > should be cleaner to store an opaque struct along with the stack,
>> > passing its size to stack_depot_save(), and letting users access it
>> > directly using the stackdepot handler.
>> >
>> > I am also wondering if a separate hashtable mapping handlers to
>> > counters would solve the problem for you?
>>
>> Let us see first if with the changes from above the code gets to a more
>> generic and clean stage, if not we can explore further options.
>
> Alexander, does this approach sound reasonable to you?
Note this is a v4 thread; there was (and the version in mm-unstable is) v5,
where the latest was Alexander requesting further changes:
https://lore.kernel.org/all/CAG_fn%3DUJgnLFGgpkXbMeD6axZN_ifEPHvWpy2_oiPyG1a6PXng@mail.gmail.com/
> The overall feature seems useful, although I'm not seeing any positive
> reviewer feedback.
Powered by blists - more mailing lists