On Tue, Nov 24, 2015 at 10:25:54AM +0000, Patrick McHardy wrote: > Tracing might be a long running operation. The cache can go out of sync, might > be better to do a lookup on demand. We'll need to handle generations in that approach. The kernel lookup per trace will be expensive. Why not just keep the cache in userspace and update it only when needed? We can easily detect when we get out of sync via ENOBUFS. > Right now the caching infrastrucure has quite a lot of problems and I'd prefer > to get them fixed before we base new things on it. The caching infrastructure only needs to have a mode to be populated via set information, then infer existing tables from handles as you indicated. What other problems you see with it? -- 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
