From: David Miller <davem@davemloft.net>
To: mhuth@mvista.com
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [PATCH][af_key]pfkey_add: Optimize SA adds and algorithm probes
Date: Thu, 24 May 2007 17:36:27 -0700 (PDT) [thread overview]
Message-ID: <20070524.173627.98881801.davem@davemloft.net> (raw)
In-Reply-To: <46562AA2.8030102@mvista.com>
From: Mark Huth <mhuth@mvista.com>
Date: Thu, 24 May 2007 17:15:30 -0700
> I'm a bit curious why all of the crypto modules got loaded, but it
> doesn't matter.
When SADB_REGISTER is performed on a PF_KEY socket, it calls
xfrm_probe_algs() which iterates over the lists and loads all the
availble modules.
next prev parent reply other threads:[~2007-05-25 0:36 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
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 [this message]
-- 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=20070524.173627.98881801.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=mhuth@mvista.com \
--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).