From: Steffen Klassert <steffen.klassert@secunet.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: "herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
<David.Laight@ACULAB.COM>
Subject: Re: [PATCH v2] xfrm: branchless addr4_match() on 64-bit
Date: Mon, 27 Mar 2017 12:37:19 +0200 [thread overview]
Message-ID: <20170327103719.GI23004@secunet.com> (raw)
In-Reply-To: <20170325164117.GB4950@avx2>
On Sat, Mar 25, 2017 at 07:41:17PM +0300, Alexey Dobriyan wrote:
> Current addr4_match() code has special test for /0 prefixes because of
> standard required undefined behaviour. However, it is possible to omit
> it on 64-bit because shifting can be done within a 64-bit register and
> then truncated to the expected value (which is 0 mask).
>
> Implicit truncation by htonl() fits nicely into R32-within-R64 model
> on x86-64.
>
> Space savings: none (coincidence)
> Branch savings: 1
>
> Before:
>
> movzx eax,BYTE PTR [rdi+0x2a] # ->prefixlen_d
> test al,al
> jne xfrm_selector_match + 0x23f
> ...
> movzx eax,BYTE PTR [rbx+0x2b] # ->prefixlen_s
> test al,al
> je xfrm_selector_match + 0x1c7
>
> After (no branches):
>
> mov r8d,0x20
> mov rdx,0xffffffffffffffff
> mov esi,DWORD PTR [rsi+0x2c]
> mov ecx,r8d
> sub cl,BYTE PTR [rdi+0x2a]
> xor esi,DWORD PTR [rbx]
> mov rdi,rdx
> xor eax,eax
> shl rdi,cl
> bswap edi
>
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Also applied to ipsec-next, thanks for the patches Alexey!
next prev parent reply other threads:[~2017-03-27 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 23:32 [PATCH] xfrm: branchless addr4_match() on 64-bit Alexey Dobriyan
2017-03-24 17:16 ` David Laight
2017-03-25 16:37 ` Alexey Dobriyan
2017-03-25 16:41 ` [PATCH v2] " Alexey Dobriyan
2017-03-27 10:37 ` Steffen Klassert [this message]
2017-03-27 13:11 ` Alexey Dobriyan
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=20170327103719.GI23004@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=David.Laight@ACULAB.COM \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.