netdev - Re: [PATCH] ipv4: fix ipsec forward performance regression

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]

Date:	Thu, 03 Nov 2011 22:43:29 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	kim.phillips@...escale.com
Cc:	stable@...r.kernel.org, eric.dumazet@...il.com,
	zheng.z.yan@...el.com, netdev@...r.kernel.org
Subject: Re: [PATCH] ipv4: fix ipsec forward performance regression

From: Kim Phillips <kim.phillips@...escale.com>
Date: Thu, 3 Nov 2011 13:58:51 -0500

> I see b732339 (ipv4: fix ipsec forward performance regression) has
> been added to the 3.0- and 3.1-stable trees.
> 
> b732339 increases IPSec fwding performance from 0.2kpps to ~3.5kpps.
> 
> However, adding upstream commit aa1c366 (net: Handle different key
> sizes between address families in flow cache) brings performance
> back up to 2.6.38 levels, i.e., ~44kpps.
> 
> So can aa1c366 also be queued to the v2.6.39 and v3.0 stable
> trees?

1) stable@...nel.org no longer exists and will just go into the bit
   bucket, it's now stable@...r.kernel.org

2) The patch in question doesn't apply cleanly to v3.0.8 -stable so
   if it's important to you you'll need to submit a backport.

3) 2.6.39 is no longer a maintained -stable kernel series.
--
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