netdev - RE: CPU usage for IPSec in Linux 2.6.38

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <A2354B6A9F807641B21EEABD666ECEEA02596EEE@XMB-BGL-416.cisco.com>
Date:	Wed, 11 Jan 2012 12:39:07 +0530
From:	"Naveen B N (nbn)" <nbn@...co.com>
To:	"David Miller" <davem@...emloft.net>
Cc:	<ipsec-tools-devel@...ts.sourceforge.net>, <netdev@...r.kernel.org>
Subject: RE: CPU usage for IPSec in Linux 2.6.38

Hi David,
Thanks for the early reply .

I can't have a wild card has my outer IP address
Are unique for across Ipsec Tunnle > 6000, so 
I this case I have to add all the policies for 
Which the selectors my have a wild card but 
Outer IP address are specific and unique.

So taught of optimizing my just adding the policy 
Entry without the actual checking the previous list 
In kernel.

Is there better way of doing it David.

Thanks and Regards
Naveen

-----Original Message-----
From: David Miller [mailto:davem@...emloft.net] 
Sent: Wednesday, January 11, 2012 12:05 PM
To: Naveen B N (nbn)
Cc: ipsec-tools-devel@...ts.sourceforge.net; netdev@...r.kernel.org
Subject: Re: CPU usage for IPSec in Linux 2.6.38

From: "Naveen B N (nbn)" <nbn@...co.com>
Date: Wed, 11 Jan 2012 08:20:12 +0530

> Did anybody try creating IPSec Tunnels > 6000 in Linux
> And faced the same problem below.

The problem is that you must situate your rules according to
certain rules otherwise performance will suffer greatly.

You must:

1) Predominantly use fully specified, non-wildcard, rules.

   These go into a special hash table which approaches complexity
   O(1).

2) If you absolutely must have wildcarded rules, only have an
   extremely small number of them.

   These go onto a linked list which is O(N).

There is no reasonable reason to have thousands of wildcarded
rules.

Thousands of fully specified non-wildcard rules are reasonable,
and what we optimize the IPSEC datastructures for.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html