Re: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49

Stephen Hemminger
2009-04-11T15:08:13Z

On Sat, 11 Apr 2009 07:14:50 +0200 (CEST)
Jan Engelhardt <jengelh@medozas.de> wrote:

>
> On Saturday 2009-04-11 06:15, Paul E. McKenney wrote:
> >On Fri, Apr 10, 2009 at 06:39:18PM -0700, Linus Torvalds wrote:
> >>An unhappy user reported:
> >>>>> Adding 200 records in iptables took 6.0sec in 2.6.30-rc1 compared to
> >>>>> 0.2sec in 2.6.29. I've bisected down this commit.
> >>>>> 784544739a25c30637397ace5489eeb6e15d7d49
> >>
> >> I wonder if we should bring in the RCU people too, for them to tell you
> >> that the networking people are beign silly, and should not synchronize
> >> with the very heavy-handed
> >>
> >> synchronize_net()
> >>
> >> but instead of doing synchronization (which is probably why adding a few
> >> hundred rules then takes several seconds - each synchronizes and that
> >> takes a timer tick or so), add the rules to be free'd on some rcu-freeing
> >> list for later freeing.
>
> iptables works in whole tables. Userspace submits a table, checkentry is
> called for all rules in the new table, things are swapped, then destroy
> is called for all rules in the old table. By that logic (which existed
> since dawn I think), only the swap operation needs to be locked.
>

Part of the overhead is the API choice to take counter values from user
space during the replace. If the rule replacement just always started with
zero counters it could be done with less overhead.