Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4469803imu; Tue, 8 Jan 2019 00:21:58 -0800 (PST) X-Google-Smtp-Source: ALg8bN5TNxXkEGkB+kFxzEKNEVHdPdaNITeiEgN5NdtJXoHoKkvDK77C3Q6PPkeGpV5dkpQ11hE0 X-Received: by 2002:a17:902:b83:: with SMTP id 3mr797592plr.42.1546935718363; Tue, 08 Jan 2019 00:21:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546935718; cv=none; d=google.com; s=arc-20160816; b=IcqfTwZz36HCBocD2u/J6qHYuUmgy78zO5eugMa4/ezFqzjlaTT2cN1xx3hJpfUtSr gKNV7kOLI6spvgqwIDhlp3E2s60ma0ns13mTjKdkCRlbtO/O3vZ51Ig1Qc7eniFd+iej VIAVWZJZYB9VMUmhMyAOTfXgCLnztgzdYm6pP831TcaVbHyD9LkNOdjkUKom4BrWt95J YiwOS1WA4x+WbvEVkZ4OJF8bD2xUjLK/T5g7lA4XPziAT/DzPfTz8X2nLNkVlSECiQGj iUF9m1666cZAXDmcBbGdCHN4QsGF4LhBIwTetXHZoVP9Ue9yavvmeejpMuuNwCzWCqPr 1oiQ== 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; bh=zS/RCylPQJB7e9SG6n0wu6R1HEMnW1QPH4gWedlAAlA=; b=Czbd3gjcrCAGBMpmlR84q5+L33iFuoX2cVOAWFcx/EzjHgv/7enm9wEA34Hmpjw7Qd f2CEseR6D9+t+MJi+Z8zn6BKrMsZ7HMCdC1Hk/JIGg2ugt217+B3EmeceIsTL6e0d0k7 Vh7qgNTwqjenzL/qs0GfB/dDt9Q8806PMQjgtyusNRZC4NvV8EfS+HWICTFP6cQCm7vY OMQnA/wlIHlLWQ01Ho3WOdbVfLFWvQOas7RMoNoRixz2K+HBFR2G4jQjIMp8Hou4MISV //l4k4iLq43dOIHrvsiAh8fgIm9QBiPvY482tLALV/D8iRY9o0sPp/1gXDT8z0lH5n21 8vOA== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w8si5390647pgm.467.2019.01.08.00.21.42; Tue, 08 Jan 2019 00:21:58 -0800 (PST) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728018AbfAHIUh (ORCPT + 99 others); Tue, 8 Jan 2019 03:20:37 -0500 Received: from mx2.suse.de ([195.135.220.15]:42540 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727368AbfAHIUg (ORCPT ); Tue, 8 Jan 2019 03:20:36 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 578A4AB4D; Tue, 8 Jan 2019 08:20:35 +0000 (UTC) Date: Tue, 8 Jan 2019 09:20:32 +0100 From: Michal Hocko To: Qian Cai Cc: akpm@linux-foundation.org, Pavel.Tatashin@microsoft.com, mingo@kernel.org, mgorman@techsingularity.net, iamjoonsoo.kim@lge.com, tglx@linutronix.de, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3] mm/page_owner: fix for deferred struct page init Message-ID: <20190108082032.GP31793@dhcp22.suse.cz> References: <20190103202235.GE31793@dhcp22.suse.cz> <20190104130906.GO31793@dhcp22.suse.cz> <20190104151737.GT31793@dhcp22.suse.cz> <20190104153245.GV31793@dhcp22.suse.cz> <20190107184309.GM31793@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 07-01-19 20:53:08, Qian Cai wrote: > > > On 1/7/19 1:43 PM, Michal Hocko wrote: > > On Fri 04-01-19 15:18:08, Qian Cai wrote: > > [...] > >> Though, I can't see any really benefit of this approach apart from "beautify" > > > > This is not about beautifying! This is about making the code long term > > maintainable. As you can see it is just too easy to break it with the > > current scheme. And that is bad especially when the code is broken > > because of an optimization. > > > > Understood, but the code is now fixed. If there is something fundamentally > broken in the future, it may be a good time then to create a looks like > hundred-line cleanup patch for long-term maintenance at the same time to fix > real bugs. Yeah, so revert = fix and redisign the thing to make the code more robust longterm + allow to catch more allocation. I really fail to see why this has to be repeated several times in this thread. Really. -- Michal Hocko SUSE Labs