[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <wmy3re5x2olokij77xfleomlydc7p2zczas6dagtawrl2mvh5a@d3ipt4hgqgr2>
Date: Tue, 11 Apr 2023 17:08:57 +0200
From: Michal Koutný <mkoutny@...e.com>
To: Michal Hocko <mhocko@...e.com>
Cc: Gang Li <ligang.bdlg@...edance.com>,
Waiman Long <longman@...hat.com>, cgroups@...r.kernel.org,
linux-mm@...ck.org, rientjes@...gle.com,
Zefan Li <lizefan.x@...edance.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] mm: oom: introduce cpuset oom
On Tue, Apr 11, 2023 at 03:12:34PM +0200, Michal Hocko <mhocko@...e.com> wrote:
> > Oh I see, you mean scanning all processes in all cpusets and scanning
> > all processes globally are equivalent.
>
> Why cannot you simple select a process from the cpuset the allocating
> process belongs to? I thought the whole idea was to handle well
> partitioned workloads.
Ah, I was confused by the top_cpuset implementation.
The iteration should then start in
nearest_hardwall_ancestor(task_cs(current)).
(in the 1st approximation).
The nodes_intersect/nodes_subset/nodes_equal/whatnot heuristics is
secondary.
HTH,
Michal
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists