From: <jiang.biao2@zte.com.cn>
To: mhocko@kernel.org
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org,
hillf.zj@alibaba-inc.com, minchan@kernel.org,
ying.huang@intel.com, mgorman@techsingularity.net,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
zhong.weidong@zte.com.cn
Subject: Re: [PATCH] mm/vmscan: try to optimize branch procedures.
Date: Tue, 28 Nov 2017 17:19:10 +0800 (CST) [thread overview]
Message-ID: <201711281719103258154@zte.com.cn> (raw)
In-Reply-To: <20171128080339.i3ktwm565pz7om4v@dhcp22.suse.cz>
[-- Attachment #1.1: Type: text/plain, Size: 913 bytes --]
> On Tue 28-11-17 09:49:45, Jiang Biao wrote:> > 1. Use unlikely to try to improve branch prediction. The
> > *total_scan < 0* branch is unlikely to reach, so use unlikely.
> >
> > 2. Optimize *next_deferred >= scanned* condition.
> > *next_deferred >= scanned* condition could be optimized into
> > *next_deferred > scanned*, because when *next_deferred == scanned*,
> > next_deferred shoud be 0, which is covered by the else branch.
> >
> > 3. Merge two branch blocks into one. The *next_deferred > 0* branch
> > could be merged into *next_deferred > scanned* to simplify the code.
>
> How have you measured benefit of this patch?
No accurate measurement for now.
Theoretically, unlikely could improve branch prediction for unlikely branch.
It's hard to measure the benefit of 2 and 3, any idea to do that enlightened
would be greatly appreciated. :) But it could simply code logic from coding
perspective。
next prev parent reply other threads:[~2017-11-28 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 1:49 [PATCH] mm/vmscan: try to optimize branch procedures Jiang Biao
2017-11-28 8:03 ` Michal Hocko
2017-11-28 9:19 ` jiang.biao2 [this message]
2017-11-28 9:31 ` Michal Hocko
2017-11-28 9:46 ` Mel Gorman
2017-11-28 9:40 ` Mel Gorman
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=201711281719103258154@zte.com.cn \
--to=jiang.biao2@zte.com.cn \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hillf.zj@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=ying.huang@intel.com \
--cc=zhong.weidong@zte.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).