netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart De Schuymer <bdschuym@pandora.be>
To: "David S. Miller" <davem@davemloft.net>
Cc: okir@suse.de, netdev@oss.sgi.com,
	netfilter-devel@lists.netfilter.org,
	brugolsky@telemetry-investments.com, Olaf Hering <olh@suse.de>
Subject: Re: limited number if iptable rules on 64bit hosts
Date: Thu, 03 Feb 2005 20:33:51 +0100	[thread overview]
Message-ID: <1107459231.3381.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20050203110049.6b2d9c64.davem@davemloft.net>

Op do, 03-02-2005 te 11:00 -0800, schreef David S. Miller:
> On Thu, 3 Feb 2005 19:59:28 +0100
> Olaf Hering <olh@suse.de> wrote:
> 
> >  On Thu, Feb 03, David S. Miller wrote:
> > 
> > > The rule itself is replicated per-cpu as well to keep L2 cache
> > > accesses local per cpu on SMP systems.
> > 
> > Andy made this change, which helped on a dual box.
> 
> It might not help for Olaf's 128 cpu box though :-)
> 
> I think reconsider the idea of replicating the rule itself per-cpu.
> Also, this thread should have begun with netfilter-devel at least on
> the CC:, added.

Note that ebtables only has per-cpu counters.
I wonder what limits are seen on such systems for ebtables.

cheers,
Bart

  reply	other threads:[~2005-02-03 19:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02 13:38 limited number if iptable rules on 64bit hosts Olaf Hering
2005-02-02 22:25 ` Olaf Hering
2005-02-02 22:38   ` Bill Rugolsky Jr.
2005-02-02 22:52     ` Olaf Hering
2005-02-03 11:19       ` Olaf Kirch
2005-02-03 18:48         ` David S. Miller
2005-02-03 18:59           ` Olaf Hering
2005-02-03 19:00             ` David S. Miller
2005-02-03 19:33               ` Bart De Schuymer [this message]
2005-02-03 21:35               ` Bill Rugolsky Jr.

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=1107459231.3381.3.camel@localhost.localdomain \
    --to=bdschuym@pandora.be \
    --cc=brugolsky@telemetry-investments.com \
    --cc=davem@davemloft.net \
    --cc=netdev@oss.sgi.com \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=okir@suse.de \
    --cc=olh@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).