From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f70.google.com (mail-wm0-f70.google.com [74.125.82.70]) by kanga.kvack.org (Postfix) with ESMTP id CE19E6B0387 for ; Mon, 6 Mar 2017 19:07:55 -0500 (EST) Received: by mail-wm0-f70.google.com with SMTP id d66so16152557wmi.2 for ; Mon, 06 Mar 2017 16:07:55 -0800 (PST) Received: from newverein.lst.de (verein.lst.de. [213.95.11.211]) by mx.google.com with ESMTPS id 25si11124111wrv.199.2017.03.06.16.07.54 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Mar 2017 16:07:54 -0800 (PST) Date: Tue, 7 Mar 2017 01:07:54 +0100 From: Christoph Hellwig Subject: Re: [PATCH] xfs: remove kmem_zalloc_greedy Message-ID: <20170307000754.GA9959@lst.de> References: <20170306184109.GC5280@birch.djwong.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170306184109.GC5280@birch.djwong.org> Sender: owner-linux-mm@kvack.org List-ID: To: "Darrick J. Wong" Cc: Brian Foster , Michal Hocko , Christoph Hellwig , Tetsuo Handa , Xiong Zhou , linux-xfs@vger.kernel.org, linux-mm@kvack.org, LKML , linux-fsdevel@vger.kernel.org, Michal Hocko , Dave Chinner I like killing it, but shouldn't we just try a normal kmem_zalloc? At least for the fallback it's the right thing, and even for an order 2 allocation it seems like a useful first try. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org