Hi Pablo,
Let's check table's chain list emptyness instead so struct nft_table
does not grow and we avoid the (unlikely to happen) overflow.
I prefer if you send me a patch to export the table use counter. I
think it can be useful from userspace to know if the table is used at
all and how many times it's used. I'm neither worry about the 2^32
chains limit and the extra 4 bytes per table (we'll have a small
number of tables object in memory).
What's the use case for it? I mean: knowing that the table is in use, I
can see some use case (and it could be done much simpler).
The number of chains, not really. At least right now, nothing is using
it so what could be the future need for that?
Same for chains actually.
Tomasz
--
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
