From: Mark Huth <mhuth@mvista.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH][af_key]pfkey_add: Optimize SA adds and algorithm probes
Date: Fri, 18 May 2007 10:16:59 -0700 [thread overview]
Message-ID: <464DDF8B.6090402@mvista.com> (raw)
In-Reply-To: <E1HouAO-0003i5-00@gondolin.me.apana.org.au>
Herbert Xu wrote:
> Mark Huth <mhuth@mvista.com> wrote:
>
>> This patch provides a performance optimization in the pfkey_add path.
>> Prior versions have a serious performance problem when adding a large
>> number of SAs to a node. For example, if a backup node needs to be
>> loaded with the SAs previously held by a failed active node, thousands
>> of SAs may need to be added as rapidly as possible. Tests show that
>> without this patch, such additions may take several minutes. The
>> cause is that the available algorithm modules are probed each time
>> instead of only when needed. This patch changes the unconditional
>> call to xfrm_probe_algs() to only be done when it may be needed.
>>
>
> Thanks for the patch!
>
>
>> static int pfkey_add(struct sock *sk, struct sk_buff *skb, struct
>> sadb_msg *hdr, void **ext_hdrs)
>> {
>> struct xfrm_state *x;
>> - int err;
>> + int err, probe_done = 0;
>> struct km_event c;
>>
>> - xfrm_probe_algs();
>> -
>> x = pfkey_msg2xfrm_state(hdr, ext_hdrs);
>> if (IS_ERR(x))
>> return PTR_ERR(x);
>>
>
> I don't think it works when then algorithm isn't loaded though :)
> If the algorithm isn't present pfkey_msg2xfrm_state will return
> -ENOSYS so we need to do the probe here.
>
Okay. I tested with the algorithms not loaded, and they were all loaded
after the test, but I'm sure you understand this much better than I do.
> Actually, I think we should just probe for the specific algorithm
> requested rather than everything. See patch below.
>
> [IPSEC] pfkey: Load specific algorithm in pfkey_add rather than all
>
> This is a natural extension of the changeset
>
> [XFRM]: Probe selected algorithm only.
>
> which only removed the probe call for xfrm_user. This patch does exactly
> the same thing for af_key. In other words, we load the algorithm requested
> by the user rather than everything when adding xfrm states in af_key.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>
> Cheers,
>
Thanks for the patch. I'll try it later today and confirm that it fixes
our problem.
Mark Huth
next prev parent reply other threads:[~2007-05-18 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 1:56 [PATCH][af_key]pfkey_add: Optimize SA adds and algorithm probes Mark Huth
2007-05-18 4:34 ` Herbert Xu
2007-05-18 17:16 ` Mark Huth [this message]
2007-05-18 21:21 ` Herbert Xu
2007-05-19 21:21 ` David Miller
2007-05-25 0:15 ` Mark Huth
2007-05-25 0:20 ` Herbert Xu
2007-05-25 0:36 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2007-05-11 0:59 Mark Huth
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=464DDF8B.6090402@mvista.com \
--to=mhuth@mvista.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).