linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: [GIT pull] locking/urgent for v5.15-rc2
Date: Mon, 20 Sep 2021 08:23:45 -0700	[thread overview]
Message-ID: <CAHk-=wgPrw6C-skHMLOR5PNfOtLm1Wyng3Z_eobJBz9BY+Q1ag@mail.gmail.com> (raw)
In-Reply-To: <YUhwHsx8n0KJWgQP@hirez.programming.kicks-ass.net>

On Mon, Sep 20, 2021 at 4:27 AM Peter Zijlstra <peterz@infradead.org> wrote:
>
> Is that XADD really more expensive? I don't think I've ever seen that.

Hmm. Looking at newer tables from Agner Fog, it doesn't seem to be the
big difference it used to be, so maybe not a big deal. It shows up as
many more ups, but the lock synchronization ends up dominating.

I just remember from when xadd weas new, and it was noticeably slower.

                 Linus

  reply	other threads:[~2021-09-20 15:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-19 18:28 [GIT pull] locking/urgent for v5.15-rc2 Thomas Gleixner
2021-09-19 18:28 ` [GIT pull] perf/urgent " Thomas Gleixner
2021-09-19 20:36   ` pr-tracker-bot
2021-09-19 18:28 ` [GIT pull] x86/urgent " Thomas Gleixner
2021-09-19 18:39   ` Borislav Petkov
2021-09-19 18:47     ` [GIT PULL] Updated " Borislav Petkov
2021-09-19 20:36       ` pr-tracker-bot
2021-09-19 20:10 ` [GIT pull] locking/urgent " Linus Torvalds
2021-09-20 11:27   ` Peter Zijlstra
2021-09-20 15:23     ` Linus Torvalds [this message]
2021-09-19 20:36 ` pr-tracker-bot

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='CAHk-=wgPrw6C-skHMLOR5PNfOtLm1Wyng3Z_eobJBz9BY+Q1ag@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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).