> So I'm going to fix this by consolidating identical objects into > a single rhashtable entry which also lets us get rid of the > insecure_elasticity setting. Hm. Would you rather allocate a separate head entry for the hashtable, or chain the entries? (Luckily) the colliding key case practically never happens, and some drivers don't even allow it, so that's perhaps something to keep in mind for this. Perhaps we should just generally disallow it - but a few people (hi Ben) would be really unhappy about that I guess. I think this might affect more than one use of rhashtable in mac80211 now, since the mesh paths also use it. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
