Received: by 10.223.185.116 with SMTP id b49csp4420387wrg; Mon, 26 Feb 2018 17:56:28 -0800 (PST) X-Google-Smtp-Source: AH8x225dbXj/dOfs0Cjbue56M1AfpcVSBciVfq4J8RANlfafszGjyOfitWfmry3rmuChkBFTcU6f X-Received: by 2002:a17:902:b413:: with SMTP id x19-v6mr12474771plr.420.1519696588102; Mon, 26 Feb 2018 17:56:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519696588; cv=none; d=google.com; s=arc-20160816; b=WABAi2XsaJut6DFhPgitLpopRLKhJq1J4oHc8+GislMV7wf6FJoqHSn1CDoVPeBBzT /c9jgQY3+7VWdjTshHpOd/+HcBbrhhXOdPlR5HmNRpiozDkPMLH9nCNn6MvgaW/8qTww VDKU7WBTRoovERVQgWps665BkzVFW78M3S4X3yZWGNhLEZK0zeYJkAhpJ+nm5MYYxWTF cIbpMNbPJhyW4mBlTfXTZ2revbE2UDUFBW0WdCH3wC3KifOyFTXqRJzLhCsIAzdJakmE p0xR7bStQflog/+mBrs5eU7eE5bvEmRlFDiIorYommz2XwlsJoNEAxfGJs99egb+9Qld Hz5Q== 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=v1uYHGH4gANi6I/O5DWSsRrJ3FTgVreGYunOlfIGohc=; b=j3yI0uElrTyiQabBZ0frukG1gh9W5uyDHl5DweOyvyXckVeXDfxGreswVj0AiLGunr MAf1S6D+owkvvZrERl4p0YOnsffF6ZkKlDBBQSTcs7Tm8a6Y+Z2YByzHD20o3j718QgG RPfi4VHhLeQFLfFh2nZxuE7oQtYcOJue+Z+6qNwBAQc7l41t9p+263tU111jcZh0Lvmx ac20dB781etpghwVHjTZ5qPwdoCWAFEa6akv087YHfti3hhH1umVpEX9w9it6isMFqF7 pfsW2LTk0knbZiYQG2hMMtV5XjRhpy+Yw17i3wtU1NLgBhor2Cm04iHAc+9velOVNUvH pQIA== 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 a12-v6si8023329pln.421.2018.02.26.17.56.13; Mon, 26 Feb 2018 17:56:28 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751793AbeB0BzR (ORCPT + 99 others); Mon, 26 Feb 2018 20:55:17 -0500 Received: from mga14.intel.com ([192.55.52.115]:29588 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751463AbeB0BzQ (ORCPT ); Mon, 26 Feb 2018 20:55:16 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Feb 2018 17:55:15 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,398,1515484800"; d="scan'208";a="21287066" Received: from aaronlu.sh.intel.com (HELO intel.com) ([10.239.159.135]) by orsmga006.jf.intel.com with ESMTP; 26 Feb 2018 17:55:12 -0800 Date: Tue, 27 Feb 2018 09:56:13 +0800 From: Aaron Lu To: David Rientjes Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrew Morton , Huang Ying , Dave Hansen , Kemi Wang , Tim Chen , Andi Kleen , Michal Hocko , Vlastimil Babka , Mel Gorman , Matthew Wilcox Subject: Re: [PATCH v3 1/3] mm/free_pcppages_bulk: update pcp->count inside Message-ID: <20180227015613.GA9141@intel.com> References: <20180226135346.7208-1-aaron.lu@intel.com> <20180226135346.7208-2-aaron.lu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 26, 2018 at 01:48:14PM -0800, David Rientjes wrote: > On Mon, 26 Feb 2018, Aaron Lu wrote: > > > Matthew Wilcox found that all callers of free_pcppages_bulk() currently > > update pcp->count immediately after so it's natural to do it inside > > free_pcppages_bulk(). > > > > No functionality or performance change is expected from this patch. > > > > Suggested-by: Matthew Wilcox > > Signed-off-by: Aaron Lu > > --- > > mm/page_alloc.c | 10 +++------- > > 1 file changed, 3 insertions(+), 7 deletions(-) > > > > diff --git a/mm/page_alloc.c b/mm/page_alloc.c > > index cb416723538f..3154859cccd6 100644 > > --- a/mm/page_alloc.c > > +++ b/mm/page_alloc.c > > @@ -1117,6 +1117,7 @@ static void free_pcppages_bulk(struct zone *zone, int count, > > int batch_free = 0; > > bool isolated_pageblocks; > > > > + pcp->count -= count; > > spin_lock(&zone->lock); > > isolated_pageblocks = has_isolate_pageblock(zone); > > > > Why modify pcp->count before the pages have actually been freed? When count is still count and not zero after pages have actually been freed :-) > > I doubt that it matters too much, but at least /proc/zoneinfo uses > zone->lock. I think it should be done after the lock is dropped. Agree that it looks a bit weird to do it beforehand and I just want to avoid adding one more local variable here. pcp->count is not protected by zone->lock though so even we do it after dropping the lock, it could still happen that zoneinfo shows a wrong value of pcp->count while it should be zero(this isn't a problem since zoneinfo doesn't need to be precise). Anyway, I'll follow your suggestion here to avoid confusion. > Otherwise, looks good. Thanks for taking a look at this.