From: Michal Hocko <mhocko@suse.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: hannes@cmpxchg.org, vdavydov.dev@gmail.com,
akpm@linux-foundation.org, cgroups@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 0/3] mm/memcg: some cleanup for mem_cgroup_iter()
Date: Fri, 25 Feb 2022 09:13:46 +0100 [thread overview]
Message-ID: <YhiPuokZpIk1MYaB@dhcp22.suse.cz> (raw)
In-Reply-To: <20220225003437.12620-1-richard.weiyang@gmail.com>
On Fri 25-02-22 00:34:34, Wei Yang wrote:
> No functional change, try to make it more readable.
>
> Wei Yang (3):
> mm/memcg: set memcg after css verified and got reference
> mm/memcg: set pos to prev unconditionally
> mm/memcg: move generation assignment and comparison together
>
> mm/memcontrol.c | 27 ++++++++++++---------------
> 1 file changed, 12 insertions(+), 15 deletions(-)
I am sorry but I do not really see these changes to be simplifying
the iterator code enough to be worth touching the code. The iterator
code is really subtle and we have experienced some subtle bugs there.
I would be really reluctant to touch it unless the result is a clear
simplification or a bug fix. Please keep in mind that the review
overhead is far from negligible here.
Unless Johannes sees that as a clear improvement then I would suggest
dropping these patches from the akpm's tree.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2022-02-25 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 0:34 Wei Yang
2022-02-25 0:34 ` [PATCH 1/3] mm/memcg: set memcg after css verified and got reference Wei Yang
2022-03-29 18:44 ` Johannes Weiner
2022-02-25 0:34 ` [PATCH 2/3] mm/memcg: set pos to prev unconditionally Wei Yang
2022-03-29 18:48 ` Johannes Weiner
2022-03-30 0:47 ` Wei Yang
2022-03-30 12:08 ` Johannes Weiner
2022-03-30 14:22 ` Wei Yang
2022-02-25 0:34 ` [PATCH 3/3] mm/memcg: move generation assignment and comparison together Wei Yang
2022-03-30 15:57 ` Johannes Weiner
2022-03-30 23:04 ` Wei Yang
2022-02-25 8:13 ` Michal Hocko [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=YhiPuokZpIk1MYaB@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@gmail.com \
--cc=vdavydov.dev@gmail.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