On 16.01, Thomas Graf wrote: > On 01/16/15 at 03:34pm, Patrick McHardy wrote: > > On 15.12, Thomas Graf wrote: > > > In the event of an expansion or shrinking, the new bucket table allocated > > > is exposed as a so called future table as soon as the resize process > > > starts. Lookups, deletions, and insertions will briefly use both tables. > > > The future table becomes the main table after an RCU grace period and > > > initial linking of the old to the new table was performed. Optimization > > > of the chains to make use of the new number of buckets follows only the > > > new table is in use. > > > > AFAICT nft_hash_walk() will miss new entries during this period. > > Am I missing anything here? > > A walker may not see insertions that occur after the walker was started > if resizing is enabled. Is that a problem for nftables? No, that would be Ok. The case I'm wondering about is: - insertion - resize starts - another insertion - walker, resize not finished yet -- 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
