From: Steffen Klassert <steffen.klassert@secunet.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH] xfrm: use "unsigned int" in addr_match()
Date: Mon, 27 Mar 2017 12:36:30 +0200 [thread overview]
Message-ID: <20170327103630.GH23004@secunet.com> (raw)
In-Reply-To: <20170323230750.GD31372@avx2>
On Fri, Mar 24, 2017 at 02:07:50AM +0300, Alexey Dobriyan wrote:
> x86_64 is zero-extending arch so "unsigned int" is preferred over "int"
> for address calculations and extending to size_t.
>
> Space savings:
>
> add/remove: 0/0 grow/shrink: 0/2 up/down: 0/-24 (-24)
> function old new delta
> xfrm_state_walk 708 696 -12
> xfrm_selector_match 918 906 -12
>
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Applied to ipsec-next, thanks!
prev parent reply other threads:[~2017-03-27 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 23:07 [PATCH] xfrm: use "unsigned int" in addr_match() Alexey Dobriyan
2017-03-27 10:36 ` Steffen Klassert [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=20170327103630.GH23004@secunet.com \
--to=steffen.klassert@secunet.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 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).