Re: [PATCH v2 0/3 net-next] Lockless netlink_lookup() with new concurrent hash table

On 07/31/14 at 10:46pm, David Miller wrote: > From: David Miller > Date: Thu, 31 Jul 2014 22:39:46 -0700 (PDT) > > > Looks great, series applied, thanks! > > Actually, this needs more work, reverted: > > net/netfilter/nft_hash.c: In function ‘nft_hash_destroy’: > net/netfilter/nft_hash.c:183:3:

Re: [PATCH v2 0/3 net-next] Lockless netlink_lookup() with new concurrent hash table

From: David Miller Date: Thu, 31 Jul 2014 22:39:46 -0700 (PDT) > Looks great, series applied, thanks! Actually, this needs more work, reverted: net/netfilter/nft_hash.c: In function ‘nft_hash_destroy’: net/netfilter/nft_hash.c:183:3: error: ‘ht’ undeclared (first use in this function) net/netf

Re: [PATCH v2 0/3 net-next] Lockless netlink_lookup() with new concurrent hash table

From: Thomas Graf Date: Fri, 1 Aug 2014 00:56:00 +0200 > Netlink sockets are maintained in a hash table to allow efficient lookup > via the port ID for unicast messages. However, lookups currently require > a read lock to be taken. This series adds a new generic, resizable, > scalable, concurren

[PATCH v2 0/3 net-next] Lockless netlink_lookup() with new concurrent hash table

Netlink sockets are maintained in a hash table to allow efficient lookup via the port ID for unicast messages. However, lookups currently require a read lock to be taken. This series adds a new generic, resizable, scalable, concurrent hash table based on the paper referenced in the first patch. It