From: David Laight <David.Laight@ACULAB.COM>
To: 'Alexander Duyck' <alexander.duyck@gmail.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
the arch/x86 maintainers <x86@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>
Subject: RE: [PATCH v1] x86/csum: rewrite csum_partial()
Date: Sun, 14 Nov 2021 14:21:20 +0000 [thread overview]
Message-ID: <3518c78fab894d01b391c764efffbb62@AcuMS.aculab.com> (raw)
In-Reply-To: <CAKgT0UdmECakQTinbTagiG4PWfaniP_GP6T3rLvWdP+mVrB4xw@mail.gmail.com>
From: Alexander Duyck
> Sent: 11 November 2021 21:56
...
> It might be worthwhile to beef up the odd check to account for
> anything 7 bytes or less. To address it you could do something along
> the lines of:
> unaligned = 7 & (unsigned long) buff;
> if (unaligned) {
> shift = unaligned * 8;
> temp64 = (*(unsigned long)buff >> shift) << shift;
> buff += 8 - unaligned;
> if (len < 8 - unaligned) {
> shift = (8 - len - unaligned) * 8;
> temp64 <<= shift;
> temp64 >>= shift;
> len = 0;
> } else {
> len -= 8 - unaligned;
> }
> result += temp64;
> result += result < temp64;
> }
I tried doing that.
Basically it is likely to take longer that just doing the memory reads.
The register dependency chain is just too long.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
prev parent reply other threads:[~2021-11-14 14:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 18:10 [PATCH v1] x86/csum: rewrite csum_partial() Eric Dumazet
2021-11-11 21:56 ` Alexander Duyck
2021-11-11 22:30 ` Eric Dumazet
2021-11-12 9:13 ` Peter Zijlstra
2021-11-12 14:21 ` Eric Dumazet
2021-11-12 15:25 ` Peter Zijlstra
2021-11-12 15:37 ` Eric Dumazet
2021-11-14 14:44 ` David Laight
2021-11-14 15:03 ` Eric Dumazet
2021-11-14 19:09 ` David Laight
2021-11-14 19:23 ` Eric Dumazet
2021-11-14 14:21 ` David Laight [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=3518c78fab894d01b391c764efffbb62@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.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).