On Dec 29 2007 19:54, Krzysztof Oledzki wrote: >> >> That doesn't help, the problem is that we keep only the counters on >> CPU0 up to date, but the data copied to userspace during iptables -L >> is chosen by the CPU the iptables command is running on. > > As a short-term workaround one can use taskset to force running iptables on > CPU#0. > Actually, on one (but fixed) arbitrary core. - 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
