[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150122090518.GA30859@casper.infradead.org>
Date: Thu, 22 Jan 2015 09:05:18 +0000
From: Thomas Graf <tgraf@...g.ch>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Patrick McHardy <kaber@...sh.net>, davem@...emloft.net,
paulmck@...ux.vnet.ibm.com, ying.xue@...driver.com,
netdev@...r.kernel.org, netfilter-devel@...r.kernel.org,
Eric Dumazet <edumazet@...gle.com>
Subject: Re: [PATCH 3/3] netlink: Lock out table resizes while dumping
Netlink sockets
On 01/22/15 at 06:20pm, Herbert Xu wrote:
> On Thu, Jan 22, 2015 at 05:35:01PM +1100, Herbert Xu wrote:
> > On Wed, Jan 21, 2015 at 10:23:46AM +0000, Thomas Graf wrote:
> > >
> > > The usage will be identical to how __inet_lookup_listener() uses it.
> > > If at the end of the lookup, we ended up in a different table than
> > > we started, the lookup is restarted as an entry has moved to another
> > > table while we were moving over it.
> >
> > Who uses this stuff apart from ip_dynaddr?
>
> OK it's there for fast socket recycling. Given that and the fact
> that everyone seems to be happy with restarting the dump after a
> resize, I think we should just go with that.
>
> Anybody who wants a better walk can always implement their own
> data structure outside of rhashtable.
What did you think of the idea to let the user store the walker
bit for rhashtable?
--
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