mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Xiangyang Yu <yuxiangyang4@huawei.com>,
	mingo@redhat.com, peterz@infradead.org, dvhart@infradead.org
Cc: linux-kernel@vger.kernel.org, yuxiangyang4@Huawei.com
Subject: Re: [PATCH] kernel/futex: Change pi_state_update_owner() to an inline function
Date: Thu, 11 Mar 2021 17:06:20 +0100	[thread overview]
Message-ID: <874khh4qv7.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20210309024012.1391035-1-yuxiangyang4@huawei.com>

On Tue, Mar 09 2021 at 10:40, Xiangyang Yu wrote:
> In our performance tests, we find that the performance of
> sysbench is descend. Function call consumes too many instructions,
> change pi_state_update_owner() to an inline function.

Serioulsy? sysbench does not use PI futexes which means that it does not
ever invoke this function. So it's completely irrelevant for that test
whether the function is marked inline or not.

Aside of that the compiler can ignore 'inline' or inline a static
function. But even if there would be an extra call, then

> Test case: https://github.com/akopytov/sysbench
> Test cmd: ./sysbench --test=threads --num-threads=$thr
>               --thread-yields=100 --thread-locks=2 run
>
> $thr    stock   non-inline   inline
> 256    0.8511     0.9254     0.8588
> 512    0.8489     0.9232     0.8503
> 1024   0.8347     0.9248     0.8495
> 2048   0.8338     0.9575     0.8402

a performance change of this magnitude is certainly not the result. I
also have no idea what these numbers actually mean. Nothing in a
sysbench output with the same parameters looks even close.

But whatever the above is, the 'inline' is neither the cause nor the
cure.

Thanks,

        tglx

      reply	other threads:[~2021-03-11 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09  2:40 Xiangyang Yu
2021-03-11 16:06 ` Thomas Gleixner [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=874khh4qv7.fsf@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yuxiangyang4@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 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®