mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Feng Tang <feng.tang@intel.com>
Cc: kernel test robot <oliver.sang@intel.com>,
	Lee Jones <lee.jones@linaro.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Russell King <linux@armlinux.org.uk>,
	Peilin Ye <yepeilin.cs@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org, lkp@intel.com, ying.huang@intel.com,
	zhengjun.xing@intel.com
Subject: Re: [Fonts]  9522750c66:  fio.read_iops 7.5% improvement
Date: Sat, 14 Nov 2020 13:25:44 +0100	[thread overview]
Message-ID: <X6/MyFRkEPGqnNtK@kroah.com> (raw)
In-Reply-To: <20201114071916.GA71316@shbuild999.sh.intel.com>

On Sat, Nov 14, 2020 at 03:19:17PM +0800, Feng Tang wrote:
> Hi Greg,
> 
> On Fri, Nov 13, 2020 at 07:46:57AM +0100, Greg Kroah-Hartman wrote:
> > On Thu, Nov 12, 2020 at 10:06:25PM +0800, kernel test robot wrote:
> > > 
> > > Greeting,
> > > 
> > > FYI, we noticed a 7.5% improvement of fio.read_iops due to commit:
> > > 
> > > 
> > > commit: 9522750c66c689b739e151fcdf895420dc81efc0 ("Fonts: Replace discarded const qualifier")
> > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> > 
> > I strongly doubt this :)
> 
> We just double checked, the test was run 4 times and the result are
> very stable.
> 
> The commit does looks irrelevant to fio test, and we just further
> checked the System map of the 2 kernels, and many data's alignment
> have been changed (systemmaps attached).
> 
> We have a hack debug patch to make data sections of each .o file to
> be aligned, with that the fio result gap could be reduced from +7.5%
> to +3.8%, so there is still some other factor affecting the benchmark,
> which need more checking. And with the same debug method of forcing
> data sections aligned, 2 other strange performance bumps[1][2] reported
> by 0day could be recovered.
> 
> [1]. https://lore.kernel.org/lkml/20200205123216.GO12867@shao2-debian/
> [2]. https://lore.kernel.org/lkml/20200305062138.GI5972@shao2-debian/

That's really odd.  Why wouldn't .o sections be aligned already and how
does that affect the real .ko files that are created from that?  What
alignment are you forcing?

And also, what hardware is seeing this performance gains?  Something is
fitting into a cache now that previously wasn't, and tracking that down
seems like it would be very worthwhile as that is a non-trivial speedup
that some developers take years to achieve with code changes.

thanks,

greg k-h

  parent reply	other threads:[~2020-11-14 12:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 14:06 kernel test robot
2020-11-13  6:46 ` Greg Kroah-Hartman
2020-11-13  7:14   ` Lee Jones
     [not found]   ` <20201114071916.GA71316@shbuild999.sh.intel.com>
2020-11-14 12:25     ` Greg Kroah-Hartman [this message]
2020-11-15 12:40       ` Feng Tang

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=X6/MyFRkEPGqnNtK@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=feng.tang@intel.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=oliver.sang@intel.com \
    --cc=yepeilin.cs@gmail.com \
    --cc=ying.huang@intel.com \
    --cc=zhengjun.xing@intel.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

all inboxes | Powered by JetHome®