netdev - [PATCH 0/7] caching bundles, iteration 2

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-next>] [day] [month] [year] [list]

Date:	Mon, 29 Mar 2010 17:12:37 +0300
From:	Timo Teras <timo.teras@....fi>
To:	netdev@...r.kernel.org
Cc:	Herbert Xu <herbert@...dor.apana.org.au>,
	Timo Teras <timo.teras@....fi>
Subject: [PATCH 0/7] caching bundles, iteration 2

This is the current dump of my working tree. The first three
patches should be good already.

The patches 4-7 are more of experimental. And patch 6 has
currently a "bundle leak". If we have per-socket policy that
results in requiring a bundle, it's never freed. I'm not yet
exactly sure how to deal with that. Probably should keep the
bundles not associated with a flow cache entry in their own
global list, which should get garbage collected periodically.

Timo Teras (7):
  xfrm: remove policy lock when accessing policy->walk.dead
  flow: structurize flow cache
  flow: allocate hash table for online cpus only
  flow: delayed deletion of flow cache entries
  flow: virtualize get and entry deletion methods
  xfrm: cache bundles instead of policies for outgoing flows
  xfrm: remove policy garbage collection

 include/net/flow.h      |   18 +-
 include/net/xfrm.h      |   12 +-
 net/core/flow.c         |  442 +++++++++++++++----------
 net/ipv4/xfrm4_policy.c |   22 --
 net/ipv6/xfrm6_policy.c |   31 --
 net/xfrm/xfrm_policy.c  |  831 ++++++++++++++++++++++++-----------------------
 net/xfrm/xfrm_user.c    |    6 +-
 7 files changed, 712 insertions(+), 650 deletions(-)

--
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