On 02/23/15 at 10:49am, Paul E. McKenney wrote: > Hello! > > Alexei mentioned that there was some excitement a couple of weeks ago in > Ottawa, something about the resizing taking forever when there were large > numbers of concurrent additions. One approach comes to mind: @Dave et al, Just want to make sure we have the same level of understanding of urgency for this. The only practical problem experienced so far is loading n*1M entries into an nft_hash set which takes 3s for 4M entries upon restore. A regular add is actually fine as it provides a hint and sizes the table accordingly. I agree that rhashtable should be improved to better handle many inserts on small tables but wanted to make sure whether anyone thinks this needs urgent fixing in 3.20 or whether we can take some time to fully understand all scenarios and experiment with ideas and then propose solutions for the next merge window. I also have the TCP hash tables on my radar while improving this. -- 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
