From: David Miller <davem@davemloft.net>
To: tgraf@suug.ch
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] rhashtable: Round up/down min/max_size to ensure we respect limit
Date: Thu, 19 Mar 2015 21:02:46 -0400 (EDT) [thread overview]
Message-ID: <20150319.210246.835966531852513271.davem@davemloft.net> (raw)
In-Reply-To: <20150319223113.GD4190@casper.infradead.org>
From: Thomas Graf <tgraf@suug.ch>
Date: Thu, 19 Mar 2015 22:31:13 +0000
> Round up min_size respectively round down max_size to the next power
> of two to make sure we always respect the limit specified by the
> user. This is required because we compare the table size against the
> limit before we expand or shrink.
>
> Also fixes a minor bug where we modified min_size in the params
> provided instead of the copy stored in struct rhashtable.
>
> Signed-off-by: Thomas Graf <tgraf@suug.ch>
> ---
> Herbert: I'm fine with either approach. I figured you expected the
> user to take care of this, hence the added warning. This is perfectly
> fine with me me as well.
Applied, thanks a lot.
next prev parent reply other threads:[~2015-03-20 1:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 16:34 [PATCH net-next] rhashtable: Warn if min_size or max_size are not a power of two Thomas Graf
2015-03-19 19:24 ` David Miller
2015-03-19 19:46 ` [PATCH net-next v2] " Thomas Graf
2015-03-19 21:02 ` Herbert Xu
2015-03-19 21:15 ` Thomas Graf
2015-03-19 21:49 ` Herbert Xu
2015-03-19 22:02 ` Herbert Xu
2015-03-19 22:31 ` [PATCH net-next] rhashtable: Round up/down min/max_size to ensure we respect limit Thomas Graf
2015-03-19 22:41 ` Herbert Xu
2015-03-20 1:02 ` David Miller [this message]
2015-03-20 10:57 ` [PATCH net-next v2] rhashtable: Warn if min_size or max_size are not a power of two David Laight
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=20150319.210246.835966531852513271.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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).