From: Linus Torvalds <torvalds@linux-foundation.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Borislav Petkov <bp@alien8.de>,
Noah Goldstein <goldstein.w.n@gmail.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86/misc for 6.5
Date: Tue, 27 Jun 2023 15:25:41 -0700 [thread overview]
Message-ID: <CAHk-=wiQEj1cP7tnQ6Uw1jjFYnZmMdNgodga3b+rw98vBBvENg@mail.gmail.com> (raw)
In-Reply-To: <1982e4b4-3858-d456-6c90-92782b95726a@linux.intel.com>
On Tue, 27 Jun 2023 at 14:44, Arjan van de Ven <arjan@linux.intel.com> wrote:
>
> fwiw long flights and pools have a relation; I made a userspace testbench
> for this some time ago: https://github.com/fenrus75/csum_partial
> in case one would actually WANT to test ;)
Hmm.
I don't know what the rules are - and some of the functions you test
seem actively buggy (ie not handling alignment right etc).
But on my machine I get:
02: 8.6 / 10.4 cycles (e29e455e) Upcoming linux kernel version
04: 8.6 / 10.4 cycles (e29e455e) Specialized to size 40
06: 7.7 / 9.5 cycles (e29e455e) New version
22: 8.7 / 9.6 cycles (e29e455e) Odd-alignment handling removed
...
which would seem to mean that my code ("New version") is doing well.
It does do worse on the "odd alignment" case:
03: 15.5 / 17.8 cycles (00006580) Upcoming linux kernel version
05: 15.5 / 17.8 cycles (00006580) Specialized to size 40
07: 16.6 / 19.5 cycles (0000bc29) New version
23: 8.8 / 8.6 cycles (1de29e47) Odd-alignment handling removed
...
I just hacked the code into the benchmark without looking too closely
at what is going on, so no guarantees.
Linus
next prev parent reply other threads:[~2023-06-27 22:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 11:00 [GIT PULL] x86/misc for 6.5 Borislav Petkov
2023-06-27 20:11 ` Linus Torvalds
2023-06-27 20:26 ` Linus Torvalds
2023-06-27 20:38 ` Borislav Petkov
2023-06-27 20:49 ` Linus Torvalds
2023-06-27 21:11 ` Borislav Petkov
2023-06-27 21:44 ` Linus Torvalds
2023-06-27 21:58 ` Linus Torvalds
2023-06-27 21:44 ` Arjan van de Ven
2023-06-27 22:25 ` Linus Torvalds [this message]
2023-06-27 22:43 ` Linus Torvalds
2023-06-27 22:50 ` Arjan van de Ven
2023-06-27 23:02 ` Linus Torvalds
2023-06-27 23:05 ` Arjan van de Ven
2023-06-29 5:29 ` Herbert Xu
2023-06-27 20:52 ` 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-=wiQEj1cP7tnQ6Uw1jjFYnZmMdNgodga3b+rw98vBBvENg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=goldstein.w.n@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).