From: Bart De Schuymer <bdschuym@pandora.be>
To: Harald Welte <laforge@netfilter.org>
Cc: netfilter-devel@lists.netfilter.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] fix iptables on systems with discontiguous processor ids
Date: Tue, 11 Oct 2005 17:15:01 +0000 [thread overview]
Message-ID: <1129050901.3378.17.camel@localhost.localdomain> (raw)
In-Reply-To: <20051011104446.GJ4290@rama>
Op di, 11-10-2005 te 12:44 +0200, schreef Harald Welte:
> On Mon, Oct 10, 2005 at 02:15:18PM -0700, David S. Miller wrote:
> > Ebtables needs it too. "git grep num_possible_cpus" shows all
> > of the users in the whole tree, %80 of which are the netfilter
> > cases we're fixing here :-)
>
> mh. I'm not very familiar with the ebtables specific changes, and
> apparently it differs quite a bit in counter handling.
Counters are allocated separately from the rules so that rules don't
need to be duplicated for each cpu. But the fix for ebtables should be
very similar to the one for iptables.
> Anyway, I've tried to come up with a patch that also includes ebtables.
>
> Bart: Could you please comment on it? If you have missed the previous
> thread: some systems have smp processor id's "0 2" but no "1", e.g.
> num_possible_cpus() is 2 (and we allocate two rulesets), but then we try
> to index it with '2', e.g. the non-existing 3rd copy.
I will once I can see it :)
cheers,
Bart
next prev parent reply other threads:[~2005-10-11 17:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 16:41 [PATCH] fix iptables on systems with discontiguous processor ids Harald Welte
2005-10-10 21:15 ` David S. Miller
2005-10-10 21:41 ` Patrick McHardy
2005-10-10 21:52 ` Patrick McHardy
2005-10-10 22:06 ` David S. Miller
2005-10-11 14:23 ` Harald Welte
2005-10-11 19:39 ` David S. Miller
2005-10-12 6:36 ` Harald Welte
2005-10-10 22:04 ` David S. Miller
2005-10-10 21:46 ` Harald Welte
2005-10-11 13:54 ` Henrik Nordstrom
2005-10-11 14:13 ` Eric Dumazet
2005-10-11 17:45 ` Harald Welte
2005-10-11 22:57 ` David S. Miller
2005-10-12 7:00 ` Harald Welte
2005-10-13 22:01 ` Eric Dumazet
2005-10-17 4:18 ` David S. Miller
2005-10-11 10:44 ` Harald Welte
2005-10-11 17:15 ` Bart De Schuymer [this message]
2005-10-11 17:55 ` Harald Welte
2005-10-11 17:54 ` Harald Welte
2005-10-11 21:54 ` Sébastien Bernard
2005-10-11 22:32 ` David S. Miller
2005-10-12 6:22 ` seb
2005-10-12 6:31 ` David S. Miller
2005-10-12 7:04 ` Sébastien Bernard
2005-10-12 7:34 ` David S. Miller
2005-10-12 6:43 ` Harald Welte
2005-10-12 22:54 ` David S. Miller
2005-10-13 7:18 ` seb
2005-10-13 19:11 ` David S. Miller
2005-10-13 8:46 ` Herbert Xu
2005-10-13 21:14 ` David S. Miller
2005-10-13 22:37 ` seb
2005-10-14 18:33 ` Harald Welte
2005-10-10 21:48 ` Sébastien Bernard
2005-10-11 14:23 ` Harald Welte
2005-10-11 20:59 ` Sébastien Bernard
2005-10-11 21:33 ` David S. Miller
2005-10-12 6:40 ` Harald Welte
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=1129050901.3378.17.camel@localhost.localdomain \
--to=bdschuym@pandora.be \
--cc=davem@davemloft.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.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.