Re: rhashtable: Use __vmalloc with GFP_ATOMIC for table allocation

Herbert Xu
2015-12-09T02:25:14Z

On Wed, Dec 09, 2015 at 03:18:26AM +0100, Thomas Graf wrote:
>
> Assuming that we only encounter this scenario with very large
> table sizes, it might be OK to assume that deferring the actual
> resize via the worker thread while continuing to insert above
> 100% utilization in atomic context is safe.

As test_rhashtable has demonstrated already this approach doesn't
work. There is nothing in the kernel that will ensure that the
worker thread gets to run at all.

Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt