Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp1157615imm; Fri, 22 Jun 2018 11:16:45 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKG5T26Cq74cj070vluj4oqSHwtsCrj3Nw2SHXTFiZd4Cp29kNoxrXhqAwXBBHHg+DpL7sb X-Received: by 2002:a17:902:714e:: with SMTP id u14-v6mr2764749plm.289.1529691405656; Fri, 22 Jun 2018 11:16:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529691405; cv=none; d=google.com; s=arc-20160816; b=Lgyg0u8d7YKd2hLUniMgn4wysEA3jUq/kA9Z+ky/I3BDcwTKkyoPvsXFHJAiHjHe48 RNXrUDXYcZYhRxHI3myOeG6Ja8U3dCAClTHXYCBlAvDIFnM8yav7q+sKHZwP6JqbsOSX oNPWk9OyoZEQNOJTP05DBKe4w8DEAX4txlEQvLyucOeln9ApTvd/patRQ2BCnmKZZidX B21CWBBhZUElk94dkj+nqSsMOfJyAH39cFmWW8mSOWBt6EDSvZ/sTzx+i3USb7fK7bUJ nY85PBjj9SngEyld+Qpe4TGJrWUqLF343BIHvTxd5xy6p9UHpRdreN6WdiQagH7iM2Df mMAQ== 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=RreFVXfanJDXFp2Q/0V2QfnU4X4ss2l4jN6DNsFi1nc=; b=FFpEavB5c1bXznv+WTKQ9vLjP1ikl87knsZNq+HtAADDp6ACmJsderWZFKpcM3NFpm zq3xCJ8yIARRx43Lu1PHwUx2dzQjff1XUge9jKDYn6Kuny4zYYhuv9DVQxIdnPwbqgWK jFDdDxSNbRtWcVva2CK2Vo/Y6y1zd7CLX7x+2KEfZ6lKK1D46/V7mL2qTIUzwrAAta+y zRnJr6pfKH5Mn5IgF+Yo3m9TF6lXC+Q5SPFOzONWqr5wIN43JK1NSejnvW1ccumwY709 DRv5A3wuOfSouoQdIPL9UMwXHZkItYLDH1pzgMrlkAKhOp2ae1bXZ1OgWeFemXrwBOjy 8gGQ== 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 m3-v6si8048917pfc.312.2018.06.22.11.16.29; Fri, 22 Jun 2018 11:16:45 -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 S933969AbeFVSPt (ORCPT + 99 others); Fri, 22 Jun 2018 14:15:49 -0400 Received: from mx2.suse.de ([195.135.220.15]:52822 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933585AbeFVSPs (ORCPT ); Fri, 22 Jun 2018 14:15:48 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (charybdis-ext-too.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 775C3AD20; Fri, 22 Jun 2018 18:15:46 +0000 (UTC) Date: Fri, 22 Jun 2018 11:15:40 -0700 From: Davidlohr Bueso To: akpm@linux-foundation.org, torvalds@linux-foundation.org Cc: tgraf@suug.ch, herbert@gondor.apana.org.au, manfred@colorfullife.com, mhocko@kernel.org, guillaume.knispel@supersonicimagine.com, linux-api@vger.kernel.org, linux-kernel@vger.kernel.org, Davidlohr Bueso Subject: [PATCH v2 1/4] lib/rhashtable: simplify bucket_table_alloc() Message-ID: <20180622181540.5gul4lx5dteqzzk3@linux-r8p5> References: <20180621212825.3059-1-dave@stgolabs.net> <20180621212825.3059-2-dave@stgolabs.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20180621212825.3059-2-dave@stgolabs.net> 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 As of ce91f6ee5b3 (mm: kvmalloc does not fallback to vmalloc for incompatible gfp flag), we can simplify the caller and trust kvzalloc() to just do the right thing. For the case of the GFP_ATOMIC context, we can drop the __GFP_NORETRY flag for obvious reasons, and for the __GFP_NOWARN case, however, it is changed such that the caller passes the flag instead of making bucket_table_alloc() handle it. This slightly changes the gfp flags passed on to nested_table_alloc() as it will now also use GFP_ATOMIC | __GFP_NOWARN. However, I consider this a positive consequence as for the same reasons we want nowarn semantics in bucket_table_alloc(). Signed-off-by: Davidlohr Bueso --- v2: - Changes based on Neil's concerns about keeping nowarn flag. - Better changelog. lib/rhashtable.c | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/lib/rhashtable.c b/lib/rhashtable.c index 9427b5766134..083f871491a1 100644 --- a/lib/rhashtable.c +++ b/lib/rhashtable.c @@ -175,10 +175,7 @@ static struct bucket_table *bucket_table_alloc(struct rhashtable *ht, int i; size = sizeof(*tbl) + nbuckets * sizeof(tbl->buckets[0]); - if (gfp != GFP_KERNEL) - tbl = kzalloc(size, gfp | __GFP_NOWARN | __GFP_NORETRY); - else - tbl = kvzalloc(size, gfp); + tbl = kvzalloc(size, gfp); size = nbuckets; @@ -459,7 +456,7 @@ static int rhashtable_insert_rehash(struct rhashtable *ht, err = -ENOMEM; - new_tbl = bucket_table_alloc(ht, size, GFP_ATOMIC); + new_tbl = bucket_table_alloc(ht, size, GFP_ATOMIC | __GFP_NOWARN); if (new_tbl == NULL) goto fail; -- 2.16.4