netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: tgraf@suug.ch
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] bridge: Fix enforcement of multicast hash_max limit
Date: Mon, 16 Jul 2012 22:59:46 -0700 (PDT)	[thread overview]
Message-ID: <20120716.225946.92115650026078905.davem@davemloft.net> (raw)
In-Reply-To: <417e2d4ff99d88014f288e9924c5a45d4650f474.1341995313.git.tgraf@suug.ch>

From: Thomas Graf <tgraf@suug.ch>
Date: Wed, 11 Jul 2012 10:29:19 +0200

> The hash size is doubled when it needs to grow and compared against
> hash_max. The >= comparison will limit the hash table size to half
> of what is expected i.e. the default 512 hash_max will not allow
> the hash table to grow larger than 256.
> 
> Also print the hash table limit instead of the desirable size when
> the limit is reached.
> 
> Signed-off-by: Thomas Graf <tgraf@suug.ch>

Applied to net-next, thanks Thomas.

      reply	other threads:[~2012-07-17  5:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11  8:29 [PATCH] bridge: Fix enforcement of multicast hash_max limit Thomas Graf
2012-07-17  5:59 ` David Miller [this message]

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=20120716.225946.92115650026078905.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=tgraf@suug.ch \
    /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).