[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D5A6C2E7-2AB1-46D0-8876-2D6AAAA3937F@appneta.com>
Date: Wed, 23 Jan 2019 19:40:01 -0800
From: Josh Elsasser <jelsasser@...neta.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: "David S . Miller" <davem@...emloft.net>,
Thomas Graf <tgraf@...g.ch>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [v2 PATCH] rhashtable: Still do rehash when we get EEXIST
On Jan 23, 2019, at 7:08 PM, Herbert Xu <herbert@...dor.apana.org.au> wrote:
> Thanks for catching this!
>
> Although I think we should fix this in a different way. The problem
> here is that the shrink cannot proceed because there was a previous
> rehash that is still incomplete. We should wait for its completion
> and then reattempt a shrinnk should it still be necessary.
>
> So something like this:
SGTM.
I can't test this right now because our VM server's down after a power
outage this evening, but I tried a similar patch that swallowed the
-EEXIST err and even with that oversight the hashtable dodged the
reschedule loop.
- Josh
Powered by blists - more mailing lists