netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: David Laight <David.Laight@ACULAB.COM>,
	"davem@davemloft.net" <davem@davemloft.net>
Cc: "tgraf@suug.ch" <tgraf@suug.ch>,
	"johunt@akamai.com" <johunt@akamai.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Ying Xue <ying.xue@windriver.com>
Subject: Re: [PATCH net 1/3] rhashtable: don't test for shrink on insert, expansion on delete
Date: Fri, 20 Feb 2015 11:13:38 +0100	[thread overview]
Message-ID: <54E708D2.8030306@iogearbox.net> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1CAE675F@AcuExch.aculab.com>

On 02/20/2015 11:08 AM, David Laight wrote:
...
> Does it actually make sense to shrink below the initial default size?

rhashtable has a min_shift parameter, shrinks cannot go below that.

  reply	other threads:[~2015-02-20 10:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 23:53 [PATCH net 0/3] rhashtable updates Daniel Borkmann
2015-02-19 23:53 ` [PATCH net 1/3] rhashtable: don't test for shrink on insert, expansion on delete Daniel Borkmann
2015-02-20 10:08   ` David Laight
2015-02-20 10:13     ` Daniel Borkmann [this message]
2015-02-20 11:56       ` tgraf
2015-02-20 11:59   ` Thomas Graf
2015-02-19 23:53 ` [PATCH net 2/3] rhashtable: better high order allocation attempts Daniel Borkmann
2015-02-20 10:11   ` David Laight
2015-02-20 10:23     ` Daniel Borkmann
2015-02-20 13:46     ` Eric Dumazet
2015-02-20 14:27       ` David Laight
2015-02-20 14:31         ` tgraf
2015-02-20 14:58           ` Eric Dumazet
2015-02-20 14:54         ` Eric Dumazet
2015-02-20 12:01   ` Thomas Graf
2015-02-19 23:53 ` [PATCH net 3/3] rhashtable: allow to unload test module Daniel Borkmann
2015-02-20 12:01   ` Thomas Graf
2015-02-20 22:38 ` [PATCH net 0/3] rhashtable updates David Miller

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=54E708D2.8030306@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=David.Laight@ACULAB.COM \
    --cc=davem@davemloft.net \
    --cc=johunt@akamai.com \
    --cc=netdev@vger.kernel.org \
    --cc=tgraf@suug.ch \
    --cc=ying.xue@windriver.com \
    /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).