Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp719312ybp; Fri, 4 Oct 2019 04:00:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqycpKU3AnZ936+Y1FjYCHCXLlBHWFRgoeVt5KfKF4edkrs2hOluFfk4oym0ObnntwcU9onI X-Received: by 2002:a17:906:c72d:: with SMTP id fj13mr11965945ejb.36.1570186838722; Fri, 04 Oct 2019 04:00:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570186838; cv=none; d=google.com; s=arc-20160816; b=E+tHi/XhC5Im+oYZHgO5G4YKqpvx2wMm4g573xSS7AFzLM6YYmoZgJuc6QaX+B2Raa F/TcIbEmxh97gKDAZApsWO8ubkn82jZtmhF6/pfYaJqu/WkLnrNUn3YcUJ0oyX/O9uAH 4e3kVrj0VDRxt27ohGP0QHGsvw2NiSRxwWkmag48MHUGdwxBFOVjYNaq+yLJhYIL3jle XCOR2oyQN/OKfgii7v+iddldY7m9r+UvgdvdtqgbkIWOTZMWM0ynySH79imGrjN77ARp awPc8NgArRgAQMCFWUDkkP921nuLKJZf6S+3YphZr+HrXhOOFm/5VvbqNPqnmUcW+7fd 9CqA== 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=M4L828TtquhitwreVE/j4t+lErTxzABgFysN+QABLig=; b=CHzcEqAPbWcTzPIEcpagT9uo6Gqe/AdddqsDkpJe3QoPbuBXEI9SBozR5eb/WAey3w NIMv7/ZpmQbmPJqsUxVSGwaWfpchYEBnX82vGp1q3Jh7xwKTWHWL/4nLXExlPq/oiPlV tOL/7a0yMEcHpmktysjoc9UzQkRfvEdw9QGYKjgjlOFejMixm5nJ3rSUOdRfFV5ZZcEo hq9iROoKrlAs/56wAY6boLqYmUjRiAvjDSwPcXxjCCiylRVaZwuAX1bYvPZ0G2mk/UcC EfDae2U2r3i+vOvqaZE4dVdmLa/DkqM1WaK4q7dDT19UcaDCCGVR4mxxdOQN+j8xs43C 0quw== 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 um16si2696065ejb.12.2019.10.04.04.00.14; Fri, 04 Oct 2019 04:00:38 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730723AbfJDK61 (ORCPT + 99 others); Fri, 4 Oct 2019 06:58:27 -0400 Received: from mx2.suse.de ([195.135.220.15]:55316 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730678AbfJDK61 (ORCPT ); Fri, 4 Oct 2019 06:58:27 -0400 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 8D8BCAB89; Fri, 4 Oct 2019 10:58:25 +0000 (UTC) Date: Fri, 4 Oct 2019 12:58:24 +0200 From: Michal Hocko To: Anshuman Khandual Cc: linux-mm@kvack.org, Andrew Morton , Vlastimil Babka , Oscar Salvador , Mel Gorman , Mike Rapoport , Dan Williams , Pavel Tatashin , linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm/page_alloc: Add a reason for reserved pages in has_unmovable_pages() Message-ID: <20191004105824.GD9578@dhcp22.suse.cz> References: <1570090257-25001-1-git-send-email-anshuman.khandual@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1570090257-25001-1-git-send-email-anshuman.khandual@arm.com> 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 Thu 03-10-19 13:40:57, Anshuman Khandual wrote: > Having unmovable pages on a given pageblock should be reported correctly > when required with REPORT_FAILURE flag. But there can be a scenario where a > reserved page in the page block will get reported as a generic "unmovable" > reason code. Instead this should be changed to a more appropriate reason > code like "Reserved page". Others have already pointed out this is just redundant but I will have a more generic comment on the changelog. There is essentially no information why the current state is bad/unhelpful and why the chnage is needed. All you claim is that something is a certain way and then assert that it should be done differently. That is not how changelogs should look like. -- Michal Hocko SUSE Labs