All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: gpf <gpf@simm.ru>, netfilter-devel@vger.kernel.org
Subject: Re: Quota on SMP AGAIN
Date: Sat, 29 Dec 2007 17:32:25 +0100	[thread overview]
Message-ID: <47767699.2020302@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0712281756580.29013@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Dec 28 2007 17:50, Patrick McHardy wrote:
>   
>>> And my bigtime question would be: where is the other counter
>>> actually? struct xt_quota_info only has one counter! Does
>>> netfilter secretly allocate matchinfos per-cpu?
>>>       
>> Not secretly, but yes, the entire ruleset exists once per CPU. That
>> also seems to be the problem, at the time the master idea was thought
>> of we always dumped entries from CPU 0, today its from the current
>> CPU, but the only one that actually has correct counters is CPU 0.
>>
>> The easy fix would be to revert to that behaviour, but maybe someone
>> can come up with a better idea that doesn't involve walking over the
>> entire ruleset and resycing things or adding dump callbacks to
>> matches.
>>
>>     
> Well, the short term fix would be to turn
>
> 	q->master = q
>
> into
>
> 	q->master = percpu_get(0, q)
>
> or whatever is appropriate.
>   

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.

> In the long run, separating the rule from the matchinfo data would be
> beneficial. Or actually - why cannot the ruleset exists once for all
> CPUs? The write path is a slow path anyway / it is read-mostly anyway.
>   

Mainly because of the counters, we don't want to have all CPUs fighting
for the cachelines.



  reply	other threads:[~2007-12-29 16:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-27 15:14 Quota on SMP AGAIN gpf
2007-12-27 15:54 ` Jan Engelhardt
2007-12-27 16:55   ` gpf
2007-12-28 15:26 ` Patrick McHardy
2007-12-28 15:50   ` Jan Engelhardt
2007-12-28 16:13     ` Patrick McHardy
2007-12-28 16:38       ` Jan Engelhardt
2007-12-28 16:50         ` Patrick McHardy
2007-12-28 17:00           ` Jan Engelhardt
2007-12-29 16:32             ` Patrick McHardy [this message]
2007-12-29 18:54               ` Krzysztof Oledzki
2007-12-29 19:54                 ` Jan Engelhardt
2007-12-30 17:36                   ` Patrick McHardy
2007-12-30 18:25                     ` Jan Engelhardt
2007-12-30 18:27                       ` Patrick McHardy
2007-12-30 21:31           ` Krzysztof Oledzki
2007-12-31  0:19             ` Patrick McHardy
2007-12-31  0:54               ` Jan Engelhardt
2007-12-31 14:15                 ` Patrick McHardy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47767699.2020302@trash.net \
    --to=kaber@trash.net \
    --cc=gpf@simm.ru \
    --cc=jengelh@computergmbh.de \
    --cc=netfilter-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.