From: Steffen Klassert <steffen.klassert@secunet.com>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<netdev@vger.kernel.org>, <fengguang.wu@intel.com>,
<kbuild-all@01.org>
Subject: Re: [PATCH ipsec-next v2] ipsec: add support of limited SA dump
Date: Tue, 18 Feb 2014 06:46:15 +0100 [thread overview]
Message-ID: <20140218054615.GA32371@secunet.com> (raw)
In-Reply-To: <1392388236-3093-1-git-send-email-nicolas.dichtel@6wind.com>
On Fri, Feb 14, 2014 at 03:30:36PM +0100, Nicolas Dichtel wrote:
> The goal of this patch is to allow userland to dump only a part of SA by
> specifying a filter during the dump.
> The kernel is in charge to filter SA, this avoids to generate useless netlink
> traffic (it save also some cpu cycles). This is particularly useful when there
> is a big number of SA set on the system.
>
> Note that I removed the union in struct xfrm_state_walk to fix a problem on arm.
> struct netlink_callback->args is defined as a array of 6 long and the first long
> is used in xfrm code to flag the cb as initialized. Hence, we must have:
> sizeof(struct xfrm_state_walk) <= sizeof(long) * 5.
> With the union, it was false on arm (sizeof(struct xfrm_state_walk) was
> sizeof(long) * 7), due to the padding.
> In fact, whatever the arch is, this union seems useless, there will be always
> padding after it. Removing it will not increase the size of this struct (and
> reduce it on arm).
>
> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Applied to ipsec-next, thanks Nicolas!
prev parent reply other threads:[~2014-02-18 5:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 16:46 [PATCH ipsec-next] ipsec: add support of limited SA dump Nicolas Dichtel
2014-02-14 14:30 ` [PATCH ipsec-next v2] " Nicolas Dichtel
2014-02-18 5:46 ` 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=20140218054615.GA32371@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
/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.