From: Oleg Nesterov <oleg@redhat.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Suren Baghdasaryan <surenb@google.com>,
christian.brauner@ubuntu.com, mingo@kernel.org,
peterz@infradead.org, tglx@linutronix.de, esyr@redhat.com,
christian@kellner.me, areber@redhat.com, shakeelb@google.com,
cyphar@cyphar.com, adobriyan@gmail.com,
akpm@linux-foundation.org, ebiederm@xmission.com,
gladkov.alexey@gmail.com, walken@google.com,
daniel.m.jordan@oracle.com, avagin@gmail.com,
bernd.edlinger@hotmail.de, john.johansen@canonical.com,
laoar.shao@gmail.com, timmurray@google.com, minchan@kernel.org,
kernel-team@android.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, stable@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v2 1/1] mm, oom_adj: don't loop through tasks in __set_oom_adj when not necessary
Date: Tue, 25 Aug 2020 17:44:01 +0200 [thread overview]
Message-ID: <20200825154400.GC28468@redhat.com> (raw)
In-Reply-To: <20200825150516.GJ22869@dhcp22.suse.cz>
On 08/25, Michal Hocko wrote:
>
> Btw. now that the flag is in place we can optimize __oom_kill_process as
> well.
and zap_threads().
Oleg.
next prev parent reply other threads:[~2020-08-25 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 15:30 [PATCH v2 1/1] mm, oom_adj: don't loop through tasks in __set_oom_adj when not necessary Suren Baghdasaryan
2020-08-25 11:15 ` Christian Brauner
2020-08-25 14:24 ` Suren Baghdasaryan
2020-08-25 14:40 ` Christian Brauner
2020-08-25 14:35 ` Oleg Nesterov
2020-08-25 15:05 ` Michal Hocko
2020-08-25 15:44 ` Oleg Nesterov [this message]
2020-08-25 16:34 ` Eric W. Biederman
2020-08-25 17:36 ` Suren Baghdasaryan
2020-08-25 19:12 ` Michal Hocko
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=20200825154400.GC28468@redhat.com \
--to=oleg@redhat.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=areber@redhat.com \
--cc=avagin@gmail.com \
--cc=bernd.edlinger@hotmail.de \
--cc=christian.brauner@ubuntu.com \
--cc=christian@kellner.me \
--cc=cyphar@cyphar.com \
--cc=daniel.m.jordan@oracle.com \
--cc=ebiederm@xmission.com \
--cc=esyr@redhat.com \
--cc=gladkov.alexey@gmail.com \
--cc=john.johansen@canonical.com \
--cc=kernel-team@android.com \
--cc=laoar.shao@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=shakeelb@google.com \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=timmurray@google.com \
--cc=walken@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.