Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp4540449imm; Wed, 30 May 2018 07:30:12 -0700 (PDT) X-Google-Smtp-Source: ADUXVKImwGCi5+pzewzyggANXr6ZI3tNEMny32yAarvQ883S9cwK4bCFxvyh5qax9MBG8j+bUAFH X-Received: by 2002:a62:8ac1:: with SMTP id o62-v6mr3019424pfk.141.1527690612551; Wed, 30 May 2018 07:30:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527690612; cv=none; d=google.com; s=arc-20160816; b=VHtZ+87gFqj/bHbMw7QhvGEJP2E7QZFGIJXdbI0yuMkVUevvRH1YyTaxONsPLprqiO h3zi9URIkIt1OySyw7qRTS58QWyNo9Ym12LC/Cj6JTNe8Ajfzd7NttFdISvGwvZTWWXU CsCm5/5OjiI2DNbu40qvLViTSnuyZEuOYhetAJrF1svRfXXU8gS5pu1UNjLlwcqQXKKL mjNyeAVdDL1gm9VCnxMij0GdI72ZV6JUn1gFmqAYKzrucDLXB7mgIUnwwHEsXlFXUl5o SaPCWfyklgH4KddQJdKNAUj65xgA5OqDxv15zrod3ae/G9dBNGrZ4FyeKU36mVEfZmuA PKFw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=Eh+q2/lmqu5leedAKLZt2wb7cmXXYMlbY0WBINYWcOY=; b=cbunD/w/GlsQ930qTTJrBoctwWb2Sjg8dVm/n+ASlEPvUwXE+jzAd3K2FBGVfbkYLF BQlbyu5PAR5LhRYxOavEK2GhmHDLBngLjHqzAg4pSX8X0KB7rt+Yrcill7cR+1OeeOOw Mai7jSUNGrhLR3xXUjy717CV9Z6KR8rB3vRj828eokc9XhNcPsXMkfNccCwUYomv7Ukx +4VN8HQsxhEgvtk85qFkXx4SgpjHHqnlvnBCweiMRD5gyKVHcRutC6BY6VaCjokD/ED0 jqLEND34oX6/A/PV+boPGH07y2uOzfikd17etFka2n5x8f5uRudgbYYrW65w/hSWL2RQ EnRg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e18-v6si19052363pgv.160.2018.05.30.07.29.58; Wed, 30 May 2018 07:30:12 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752751AbeE3O3a (ORCPT + 99 others); Wed, 30 May 2018 10:29:30 -0400 Received: from mx2.suse.de ([195.135.220.15]:55722 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751567AbeE3O3R (ORCPT ); Wed, 30 May 2018 10:29:17 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext-too.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 0FAB9AE4F; Wed, 30 May 2018 14:29:16 +0000 (UTC) Date: Wed, 30 May 2018 07:29:06 -0700 From: Davidlohr Bueso To: Herbert Xu Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org, tgraf@suug.ch, manfred@colorfullife.com, guillaume.knispel@supersonicimagine.com, linux-api@vger.kernel.org, linux-kernel@vger.kernel.org, Davidlohr Bueso Subject: Re: [PATCH 2/6] lib/rhashtable: guarantee initial hashtable allocation Message-ID: <20180530142906.fdib4dw2ik6smduu@linux-r8p5> References: <20180524211135.27760-1-dave@stgolabs.net> <20180524211135.27760-3-dave@stgolabs.net> <20180528094956.zaxusqqju3wtbdcz@gondor.apana.org.au> <20180529170338.7brp2m2k4gfqwf64@linux-n805> <20180529180428.l6yt6ae4oxbgrja6@gondor.apana.org.au> <20180529175927.iyea653hpgnow6p2@linux-n805> <20180529182746.t4b7tsnfma7dupom@gondor.apana.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20180529182746.t4b7tsnfma7dupom@gondor.apana.org.au> User-Agent: NeoMutt/20170912 (1.9.0) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 30 May 2018, Herbert Xu wrote: >On Tue, May 29, 2018 at 10:59:27AM -0700, Davidlohr Bueso wrote: >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? It helps in that we have two fastpath attempts before going in to __alloc_pages_slowpath() and looping in __GFP_NOFAIL. But yeah, I see your point. We can just apply KISS and avoid the extra alloc. That actually makes more sense to me now than ignoring min_size based on simplicity. Thanks for the review. Thanks, Davidlohr