Thread (33 messages) 33 messages, 4 authors, 2018-05-31

Re: [PATCH 2/6] lib/rhashtable: guarantee initial hashtable allocation

From: Herbert Xu <herbert@gondor.apana.org.au>
Date: 2018-05-29 18:28:03
Also in: lkml

On Tue, May 29, 2018 at 10:59:27AM -0700, Davidlohr Bueso wrote:
On Wed, 30 May 2018, Herbert Xu wrote:
quoted
It doesn't explain it at all.  In fact I don't see why we neeed
three attempts, just do the GFP_NOFAIL as the second and final step.
Second attempt is reduced size only as we don't want to GFP_NOFAIL
if we can avoid it helping the allocator. We go from an arbitrary
allocation to the smallest possible allocation, if all that fails
ok lets use GFP_NOFAIL. I don't know how this is not clear...
That's exactly what you need to explain in the patch or the commit
message.  In fact you still haven't explained it fully.  Why do we
need a second attempt without the GFP_NOFAIL? How does it help the
allocator?

Cheers,
-- 
Email: Herbert Xu [off-list ref]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help