From: "Michal Koutný" <mkoutny@suse.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Gang Li <ligang.bdlg@bytedance.com>,
Waiman Long <longman@redhat.com>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
rientjes@google.com, Zefan Li <lizefan.x@bytedance.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] mm: oom: introduce cpuset oom
Date: Tue, 11 Apr 2023 17:08:57 +0200 [thread overview]
Message-ID: <wmy3re5x2olokij77xfleomlydc7p2zczas6dagtawrl2mvh5a@d3ipt4hgqgr2> (raw)
In-Reply-To: <ZDVcwuiu3rWEFiTE@dhcp22.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
On Tue, Apr 11, 2023 at 03:12:34PM +0200, Michal Hocko <mhocko@suse.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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-04-11 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 6:58 Gang Li
2023-04-11 12:23 ` Michal Koutný
2023-04-11 13:04 ` Gang Li
2023-04-11 13:12 ` Michal Hocko
2023-04-11 13:17 ` Gang Li
2023-04-11 15:08 ` Michal Koutný [this message]
2023-04-11 14:36 ` Michal Hocko
2023-08-17 8:40 ` Gang Li
2023-08-17 16:45 ` Waiman Long
2023-08-22 6:31 ` Gang Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wmy3re5x2olokij77xfleomlydc7p2zczas6dagtawrl2mvh5a@d3ipt4hgqgr2 \
--to=mkoutny@suse.com \
--cc=cgroups@vger.kernel.org \
--cc=ligang.bdlg@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox