From: Dave Hansen <dave.hansen@intel.com>
To: David Laight <david.laight.linux@gmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andy Shevchenko <andy@kernel.org>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Uros Bizjak <ubizjak@gmail.com>,
linux-kernel@vger.kernel.org, Kees Cook <kees@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH next] i386: Remove string functions that use 'rep scasb'
Date: Mon, 30 Mar 2026 12:47:02 -0700 [thread overview]
Message-ID: <55d3ba47-e609-4b22-911f-047d08dc3864@intel.com> (raw)
In-Reply-To: <20260330202014.1eb6fc76@pumpkin>
On 3/30/26 12:20, David Laight wrote:
> I have Intel Quark at hand to test. But I need to know the
> step-by-step instructions on what to do.
I'll take it if it's all that we have, but Quark is really weird. It's
probably Intel's last sold 32-bit-only CPU, but it wasn't used for
anything remotely performance sensitive, it's more like a 1995 CPU than
a 2010 CPU, and Intel probably sold like twenty of them. ;)
But, seriously, we don't need to go digging in the junk heap for
performance numbers. If nobody has one handy, it's just extra
justification for "we don't care".
But let's just say *THAT* instead of doing some kind of performance
theater where we pretend that like every cycle on CPUs from 2003 matters
on a 2026 kernel, and that we even cared enough to measure it.
next prev parent reply other threads:[~2026-03-30 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260327195747.89556-1-david.laight.linux@gmail.com>
2026-03-30 16:58 ` [PATCH next] i386: Remove string functions that use 'rep scasb' Dave Hansen
2026-03-30 17:21 ` Andy Shevchenko
2026-03-30 19:20 ` David Laight
2026-03-30 19:47 ` Dave Hansen [this message]
2026-03-31 0:27 ` Maciej W. Rozycki
2026-03-31 6:59 ` Andy Shevchenko
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=55d3ba47-e609-4b22-911f-047d08dc3864@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david.laight.linux@gmail.com \
--cc=hpa@zytor.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.com \
--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