[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZWmvp5Yeb5HE1Uxo@tiehlicka>
Date: Fri, 1 Dec 2023 11:04:23 +0100
From: Michal Hocko <mhocko@...e.com>
To: Kent Overstreet <kent.overstreet@...ux.dev>
Cc: Roman Gushchin <roman.gushchin@...ux.dev>,
Qi Zheng <zhengqi.arch@...edance.com>,
Muchun Song <muchun.song@...ux.dev>,
Linux-MM <linux-mm@...ck.org>, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Dave Chinner <david@...morbit.com>
Subject: Re: [PATCH 2/7] mm: shrinker: Add a .to_text() method for shrinkers
On Thu 30-11-23 20:47:45, Kent Overstreet wrote:
> On Thu, Nov 30, 2023 at 09:14:35AM +0100, Michal Hocko wrote:
[...]
> > All that being said, I am with you on the fact that the oom report in
> > its current form could see improvements.
>
> I'm glad we're finally in agreement on something!
>
> If you want to share your own ideas on what could be improved and what
> you find useful, maybe we could find some more common ground.
One thing that I would consider an improvement is to have a way to
subscribe drivers with excessive memory consumption or those which are
struggling to dump their state.
Maybe your proposal can be extended that way but the crucial point is to
not dump all sorts of random shrinkers' state and end up with unwieldy
reports. If, on the other hand, any particular shrinker struggles to
reclaim memory and it is sitting on a lot of memory it could be able to
flag itself to be involved in the dump.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists