[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6D1CB02510@AcuExch.aculab.com>
Date: Tue, 17 Mar 2015 11:22:44 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Herbert Xu' <herbert@...dor.apana.org.au>,
"tgraf@...g.ch" <tgraf@...g.ch>
CC: David Miller <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Eric Dumazet <eric.dumazet@...il.com>
Subject: RE: [v1 PATCH 1/14] rhashtable: Remove shift from bucket_table
From: Herbert Xu
> Sent: 17 March 2015 11:01
> On Tue, Mar 17, 2015 at 10:56:57AM +0000, tgraf@...g.ch wrote:
> >
> > Given the discussions, the grow decision will likely change to
> > a max bucket length limit anyway.
>
> Actually no. In my pathces the chain length is only used to
> force an immediate rehash. Growing is still based on the number
> of elements.
>
> The reason is that the maximum (not average) chain length actually
> grows with the hash table size, even at 75% utilisation.
That doesn't surprise me.
But won't the rehashed table be just as likely to have a long list?
So you are likely to get an immediate rehash?
David
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists