From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@suse.com>,
Christian Brauner <brauner@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Jens Axboe <axboe@kernel.dk>,
Jinliang Zheng <alexjlzheng@tencent.com>,
Mateusz Guzik <mjguzik@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
Tycho Andersen <tandersen@netflix.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 0/2] memcg: deuglify mm_update_next_owner()
Date: Wed, 26 Jun 2024 22:27:28 +0200 [thread overview]
Message-ID: <20240626202727.GA17320@redhat.com> (raw)
In-Reply-To: <20240626122456.a9eb021e4ccbfbb1b6b93d1c@linux-foundation.org>
On 06/26, Andrew Morton wrote:
>
> On Wed, 26 Jun 2024 17:28:35 +0200 Oleg Nesterov <oleg@redhat.com> wrote:
>
> > On top of mm-optimize-the-redundant-loop-of-mm_update_owner_next.patch
>
> What should we do with
> mm-optimize-the-redundant-loop-of-mm_update_owner_next.patch?
Well, if you ask me (although you shoudn't ;) I think this patch makes
sense even if it can't fix all the problems.
> Further improvements (this series) can be made in the
> normal fashion?
Yes, yes. And just in case, this series mostly tries to cleanup this code
and it doesn't really depend on that patch from Jinliang.
Oleg.
prev parent reply other threads:[~2024-06-26 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 15:28 [PATCH -mm 0/2] memcg: deuglify mm_update_next_owner() Oleg Nesterov
2024-06-26 15:29 ` [PATCH 1/2] memcg: mm_update_next_owner: kill the "retry" logic Oleg Nesterov
2024-06-27 7:56 ` Michal Hocko
2024-06-27 8:29 ` Oleg Nesterov
2024-06-27 9:02 ` Michal Hocko
2024-06-26 15:29 ` [PATCH 2/2] memcg: mm_update_next_owner: move for_each_thread() into try_to_set_owner() Oleg Nesterov
2024-06-27 9:02 ` Michal Hocko
2024-06-26 19:24 ` [PATCH -mm 0/2] memcg: deuglify mm_update_next_owner() Andrew Morton
2024-06-26 20:27 ` Oleg Nesterov [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=20240626202727.GA17320@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexjlzheng@tencent.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mjguzik@gmail.com \
--cc=tandersen@netflix.com \
--cc=willy@infradead.org \
/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.