All of lore.kernel.org
 help / color / mirror / Atom feed
From: Long Li <leo.lilong@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <willy@infradead.org>, <linux-fsdevel@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <yi.zhang@huawei.com>,
	<houtao1@huawei.com>, <yangerkun@huawei.com>
Subject: Re: [PATCH] xarray: inline xas_descend to improve performance
Date: Tue, 16 Apr 2024 09:35:20 +0800	[thread overview]
Message-ID: <20240416013520.GA506789@ceph-admin> (raw)
In-Reply-To: <20240415131053.051e60135eacf281df6921f6@linux-foundation.org>

On Mon, Apr 15, 2024 at 01:10:53PM -0700, Andrew Morton wrote:
> On Mon, 15 Apr 2024 09:21:36 +0800 Long Li <leo.lilong@huawei.com> wrote:
> 
> > The commit 63b1898fffcd ("XArray: Disallow sibling entries of nodes")
> > modified the xas_descend function in such a way that it was no longer
> > being compiled as an inline function, because it increased the size of
> > xas_descend(), and the compiler no longer optimizes it as inline. This
> > had a negative impact on performance, xas_descend is called frequently
> > to traverse downwards in the xarray tree, making it a hot function.
> > 
> > Inlining xas_descend has been shown to significantly improve performance
> > by approximately 4.95% in the iozone write test.
> > 
> >   Machine: Intel(R) Xeon(R) Gold 6240 CPU @ 2.60GHz
> >   #iozone i 0 -i 1 -s 64g -r 16m -f /test/tmptest
> > 
> > Before this patch:
> > 
> >        kB    reclen    write   rewrite     read    reread
> >  67108864     16384  2230080   3637689 6 315197   5496027
> > 
> > After this patch:
> > 
> >        kB    reclen    write   rewrite     read    reread
> >  67108864     16384  2340360   3666175  6272401   5460782
> > 
> > Percentage change:
> >                        4.95%     0.78%   -0.68%    -0.64%
> > 
> > This patch introduces inlining to the xas_descend function. While this
> > change increases the size of lib/xarray.o, the performance gains in
> > critical workloads make this an acceptable trade-off.
> > 
> > Size comparison before and after patch:
> > .text		.data		.bss		file
> > 0x3502		    0		   0		lib/xarray.o.before
> > 0x3602		    0		   0		lib/xarray.o.after
> > 
> > ...
> >
> > --- a/lib/xarray.c
> > +++ b/lib/xarray.c
> > @@ -200,7 +200,7 @@ static void *xas_start(struct xa_state *xas)
> >  	return entry;
> >  }
> >  
> > -static void *xas_descend(struct xa_state *xas, struct xa_node *node)
> > +static inline void *xas_descend(struct xa_state *xas, struct xa_node *node)
> >  {
> >  	unsigned int offset = get_offset(xas->xa_index, node);
> >  	void *entry = xa_entry(xas->xa, node, offset);
> 
> I thought gcc nowadays treats `inline' as avisory and still makes up
> its own mind?
> 
> Perhaps we should use __always_inline here?

Yes, I agree with you, I will send a new version. thanks!

      reply	other threads:[~2024-04-16  1:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15  1:21 [PATCH] xarray: inline xas_descend to improve performance Long Li
2024-04-15 20:10 ` Andrew Morton
2024-04-16  1:35   ` Long Li [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=20240416013520.GA506789@ceph-admin \
    --to=leo.lilong@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=houtao1@huawei.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@infradead.org \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.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 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.