From: Peter Zijlstra <peterz@infradead.org>
To: David Laight <David.Laight@ACULAB.COM>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86: Optimise x86 IP checksum code
Date: Wed, 4 Dec 2019 10:14:50 +0100 [thread overview]
Message-ID: <20191204091450.GQ2844@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <c92db041c78e4d81a70aaf4249393901@AcuMS.aculab.com>
On Tue, Dec 03, 2019 at 11:52:09AM +0000, David Laight wrote:
> I did get about 12 bytes/clock using adox/adcx but that would need run-time
> patching and some AMD cpu that support the instructions run them very slowly.
Isn't that was we have alternative_call() for?
next prev parent reply other threads:[~2019-12-04 9:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 11:52 [PATCH] x86: Optimise x86 IP checksum code David Laight
2019-12-04 9:14 ` Peter Zijlstra [this message]
2019-12-04 10:06 ` David Laight
2019-12-06 1:45 ` kbuild test robot
2019-12-09 17:12 ` David Laight
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=20191204091450.GQ2844@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=David.Laight@ACULAB.COM \
--cc=linux-kernel@vger.kernel.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