From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Mateusz Guzik <mjguzik@gmail.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"jan.glauber@gmail.com" <jan.glauber@gmail.com>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"will@kernel.org" <will@kernel.org>
Subject: Re: [PATCH] lockref: stop doing cpu_relax in the cmpxchg loop
Date: Fri, 13 Jan 2023 17:31:39 -0600 [thread overview]
Message-ID: <CAHk-=wgTsc5z3cPo7+t2kRO1uRQML1w_o72nefyHOh8VMhqu0A@mail.gmail.com> (raw)
In-Reply-To: <SJ1PR11MB6083B48A2B2114EF833D69E2FCC29@SJ1PR11MB6083.namprd11.prod.outlook.com>
On Fri, Jan 13, 2023 at 3:47 PM Luck, Tony <tony.luck@intel.com> wrote:
>
> The computer necrophiliacs at Debian and Gentoo seem determined
> to keep ia64 alive.
>
> So perhaps this should s/cpu_relax/soemt_relax/ where soemt_relax
> is a no-op everywhere except ia64, which can define it as cpu_relax.
Heh. I already took your earlier "$ git rm -r arch/ia64" comment as an
ack for not really caring about ia64.
I suspect nobody will notice, and if ia64 is the only reason to do
this, I really don't think it would be worth it.
Linus
prev parent reply other threads:[~2023-01-13 23:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 23:36 lockref scalability on x86-64 vs cpu_relax Mateusz Guzik
2023-01-13 0:13 ` Linus Torvalds
2023-01-13 0:30 ` Luck, Tony
2023-01-13 0:45 ` Linus Torvalds
2023-01-13 7:55 ` ia64 removal (was: Re: lockref scalability on x86-64 vs cpu_relax) Ard Biesheuvel
2023-01-13 16:17 ` Luck, Tony
2023-01-13 20:49 ` Jessica Clarke
2023-01-13 21:03 ` Luck, Tony
2023-01-13 21:04 ` Jessica Clarke
2023-01-13 21:05 ` John Paul Adrian Glaubitz
2023-01-13 23:25 ` Ard Biesheuvel
2023-01-14 11:24 ` Sedat Dilek
2023-01-14 11:28 ` Sedat Dilek
2023-01-15 0:27 ` Matthew Wilcox
2023-01-15 12:04 ` Sedat Dilek
2023-01-16 9:42 ` John Paul Adrian Glaubitz
2023-01-16 9:41 ` John Paul Adrian Glaubitz
2023-01-16 13:28 ` Matthew Wilcox
2023-01-16 9:40 ` John Paul Adrian Glaubitz
2023-01-16 9:37 ` John Paul Adrian Glaubitz
2023-01-16 9:32 ` John Paul Adrian Glaubitz
2023-01-16 10:09 ` Ard Biesheuvel
2023-01-13 1:12 ` lockref scalability on x86-64 vs cpu_relax Mateusz Guzik
2023-01-13 4:08 ` Linus Torvalds
2023-01-13 9:46 ` Will Deacon
2023-01-13 3:20 ` Nicholas Piggin
2023-01-13 4:15 ` Linus Torvalds
2023-01-13 5:36 ` Nicholas Piggin
2023-01-16 14:08 ` Memory transaction instructions David Howells
2023-01-16 15:09 ` Matthew Wilcox
2023-01-16 16:59 ` Linus Torvalds
2023-01-18 9:05 ` David Howells
2023-01-19 1:41 ` Nicholas Piggin
2023-01-13 10:23 ` lockref scalability on x86-64 vs cpu_relax Peter Zijlstra
2023-01-13 18:44 ` [PATCH] lockref: stop doing cpu_relax in the cmpxchg loop Mateusz Guzik
2023-01-13 21:47 ` Luck, Tony
2023-01-13 23:31 ` Linus Torvalds [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='CAHk-=wgTsc5z3cPo7+t2kRO1uRQML1w_o72nefyHOh8VMhqu0A@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=jan.glauber@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mjguzik@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=tony.luck@intel.com \
--cc=viro@zeniv.linux.org.uk \
--cc=will@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).