From: Tejun Heo <tj@kernel.org>
To: zijun_hu <zijun_hu@zoho.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
zijun_hu@htc.com, linux-mm@kvack.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
cl@linux.com
Subject: Re: [PATCH 1/1] mm/percpu.c: simplify grouping cpu logic in pcpu_build_alloc_info()
Date: Fri, 23 Sep 2016 15:23:34 -0400 [thread overview]
Message-ID: <20160923192334.GD31387@htj.duckdns.org> (raw)
In-Reply-To: <5dcf5870-67ad-97e4-518b-645d60b0a520@zoho.com>
On Sat, Sep 24, 2016 at 02:15:09AM +0800, zijun_hu wrote:
> From: zijun_hu <zijun_hu@htc.com>
>
> simplify grouping cpu logic in pcpu_build_alloc_info() to improve
> readability and performance, it discards the goto statement too
>
> for every possible cpu, decide whether it can share group id of any
> lower index CPU, use the group id if so, otherwise a new group id
> is allocated to it
>
> Signed-off-by: zijun_hu <zijun_hu@htc.com>
I'm not gonna change that code unless there are clear upsides. It's a
complicated code path which is run once during boot. It's not worth
optimizing, the author doesn't explain how the change has been tested
or verified and doesn't respond to people pointing out that these
drive-by patches aren't helpful.
I won't engage with his patches until he changes his approach and
think that it's advisable for others to do so too.
Nacked-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-09-23 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 18:15 zijun_hu
2016-09-23 19:23 ` Tejun Heo [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=20160923192334.GD31387@htj.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=zijun_hu@htc.com \
--cc=zijun_hu@zoho.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