From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-f72.google.com (mail-ed1-f72.google.com [209.85.208.72]) by kanga.kvack.org (Postfix) with ESMTP id 9BDC76B78E0 for ; Thu, 6 Sep 2018 09:01:05 -0400 (EDT) Received: by mail-ed1-f72.google.com with SMTP id c16-v6so3651152edc.21 for ; Thu, 06 Sep 2018 06:01:05 -0700 (PDT) Received: from mx1.suse.de (mx2.suse.de. [195.135.220.15]) by mx.google.com with ESMTPS id e6-v6si4354327edd.237.2018.09.06.06.01.04 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Sep 2018 06:01:04 -0700 (PDT) Date: Thu, 6 Sep 2018 15:01:02 +0200 From: Michal Hocko Subject: Re: [RFC PATCH 07/29] memblock: remove _virt from APIs returning virtual address Message-ID: <20180906130102.GY14951@dhcp22.suse.cz> References: <1536163184-26356-1-git-send-email-rppt@linux.vnet.ibm.com> <1536163184-26356-8-git-send-email-rppt@linux.vnet.ibm.com> <20180905172017.GA2203@rapoport-lnx> <20180906072800.GN14951@dhcp22.suse.cz> <20180906124321.GD27492@rapoport-lnx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180906124321.GD27492@rapoport-lnx> Sender: owner-linux-mm@kvack.org List-ID: To: Mike Rapoport Cc: Rob Herring , linux-mm@kvack.org, Andrew Morton , davem@davemloft.net, Greg Kroah-Hartman , mingo@redhat.com, Michael Ellerman , paul.burton@mips.com, Thomas Gleixner , tony.luck@intel.com, linux-ia64@vger.kernel.org, linux-mips@linux-mips.org, linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org, Linux Kernel Mailing List On Thu 06-09-18 15:43:21, Mike Rapoport wrote: > On Thu, Sep 06, 2018 at 09:28:00AM +0200, Michal Hocko wrote: > > On Wed 05-09-18 20:20:18, Mike Rapoport wrote: > > > On Wed, Sep 05, 2018 at 12:04:36PM -0500, Rob Herring wrote: > > > > On Wed, Sep 5, 2018 at 11:00 AM Mike Rapoport wrote: > > > > > > > > > > The conversion is done using > > > > > > > > > > sed -i 's@memblock_virt_alloc@memblock_alloc@g' \ > > > > > $(git grep -l memblock_virt_alloc) > > > > > > > > What's the reason to do this? It seems like a lot of churn even if a > > > > mechanical change. > > > > > > I felt that memblock_virt_alloc_ is too long for a prefix, e.g: > > > memblock_virt_alloc_node_nopanic, memblock_virt_alloc_low_nopanic. > > > > > > And for consistency I've changed the memblock_virt_alloc as well. > > > > I would keep the current API unless the name is terribly misleading or > > it can be improved a lot. Neither seems to be the case here. So I would > > rather stick with the status quo. > > I'm ok with the memblock_virt_alloc by itself, but having 'virt' in > 'memblock_virt_alloc_try_nid_nopanic' and 'memblock_virt_alloc_low_nopanic' > reduces code readability in my opinion. Well, is _nopanic really really useful in the name. Do we even need/want implicit panic/nopanic semantic? The code should rather check for the return value and decide depending on the code path. I suspect removing panic/nopanic would make the API slightly lighter. -- Michal Hocko SUSE Labs