From: Gang Li <ligang.bdlg@bytedance.com>
To: Michal Hocko <mhocko@suse.com>
Cc: rientjes@google.com, linux-kernel@vger.kernel.org,
Waiman Long <longman@redhat.com>,
Zefan Li <lizefan.x@bytedance.com>,
cgroups@vger.kernel.org
Subject: Re: Re: Re: [PATCH v2] mm: oom: introduce cpuset oom
Date: Thu, 6 Apr 2023 16:33:27 +0800 [thread overview]
Message-ID: <1fe17d13-4b63-93ab-e6b2-3c9d09da208e@bytedance.com> (raw)
In-Reply-To: <ZC6DKM4LDOVgohpj@dhcp22.suse.cz>
I see, then let's do this as you said.
On 2023/4/6 16:30, Michal Hocko wrote:
>
> As I've said, I do not see any major concern having this behavior
> implicit, the behavior makes semantic sense and it is also much more
> likely that the selected oom victim will be a better choice than what we
> do currently. Especially on properly partitioned systems with large
> memory consumers in each partition (cpuset).
>
> That being said, I would just not add any sysctl at this stage and
> rather document the decision. If we ever encounter usecase(s) which
> would regress based on this change we can introcuce the sysctl later.
>
prev parent reply other threads:[~2023-04-06 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 11:55 Gang Li
2023-04-04 14:31 ` Michal Hocko
2023-04-04 17:24 ` Waiman Long
2023-04-06 3:04 ` Gang Li
2023-04-06 13:02 ` Gang Li
2023-04-06 15:53 ` Waiman Long
2023-04-06 3:22 ` Gang Li
2023-04-06 8:30 ` Michal Hocko
2023-04-06 8:33 ` Gang Li [this message]
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=1fe17d13-4b63-93ab-e6b2-3c9d09da208e@bytedance.com \
--to=ligang.bdlg@bytedance.com \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®