On Tue, Jan 27, 2015 at 10:15:12AM +0000, Thomas Graf wrote: > > Because libraries like libnl already handle this transparently for > various user space apps. Those apps are not even aware of the problem > and always get a consistent dump if the kernel implements INTR. Did you see Dave's message? He said those that dump need to create their own data structure so there is no point in proceeding with any of this work within rhashtable. > Because making it synchronous does not help the Netlink dump problem > at all, see below. > > Also, a sync resize causes a random inserts/removal to take a lot > longer. This leads to less predictable insert/removal times. I have > no objection to offering both sync and async resizing as long as the > choice of balance is configurable. So what? They can switch over to lockless mode if they care. The point is that for netfilter as it stands it makes no sense to go lockless because its modus operandi is to hold a single lock over everything, including walking/dumping. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
