Received: by 10.223.185.116 with SMTP id b49csp7073907wrg; Wed, 28 Feb 2018 22:29:05 -0800 (PST) X-Google-Smtp-Source: AG47ELsNpRKUTw0cN+lDE4iiMRsVYXEhRj1FCj6ZA24bFzqWxft5/PYYYe/nbWoZ5XrWsJOs7cGL X-Received: by 10.98.92.194 with SMTP id q185mr181891pfb.63.1519885745090; Wed, 28 Feb 2018 22:29:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519885745; cv=none; d=google.com; s=arc-20160816; b=UVTorTTWfVo3S5ZXlqG36DVyiEFKnMANYfCiZQxS6rJJ3+QFjk02+aQXrqnGV5q+gb 3hIeS3ZU5u8E7X82Ztcd0R71o6r2yb4oIs0coFgtqXtbgVYT4gzGiYmnEQrZuzBHldSH T/33TVCyL0nWe8hXnzs2QBMclII80UhkvYkXI8gqM2VaeGfA9gOPwBM4TZiqS7RnXNpo fn40QxMvwmJzs2FUCI7zGHGKZyN5ZKRJVKewbRCfrqVg+QgYb+TrUmNBN4DkW7UxaSIV O0lLbiC0l9RNUTWiGfaJbscLdTXrMiLBystrmabLmhaQ+omauc76pZzW8hkP1XnJZVU4 b5Jw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:arc-authentication-results; bh=p3fcq6XAfMqQVK+oJ0/kVU5co1UB+kayLuWAGT8Rv78=; b=Q82nm7j2Y30qQpl4V/gZIWnzWRp/sc44Y3IS3C035dJPPR5JwsaIEiT7sa51yDEI0p yh3A2iJoUJCUKSJvtBsWPo2mNF7IUXMHghIy92pvY6o9+7SV45DZ6POYGQ6mR05BCrID 4zmjtH1OjpVwaXgRCsenZEggSmJg6i6tx5gdP1I+G6kKfiQCgc7aizFWOm4ahjNAjqII aulQNu0C+S7oqffW4V/c8cSgdSf+827zpFtdkf5RotInm+FSUvdCqXldZKoGj6z9tbNv FNZmRS81I9O+IKkSmAk6WbokW3PePRMpYFKEzO2Id6s5yERMWmwO0f76zrl0RStWWPC9 zF5Q== 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 e1-v6si2549619pli.534.2018.02.28.22.28.50; Wed, 28 Feb 2018 22:29:05 -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 S966387AbeCAG2B (ORCPT + 99 others); Thu, 1 Mar 2018 01:28:01 -0500 Received: from mga03.intel.com ([134.134.136.65]:12103 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966378AbeCAG14 (ORCPT ); Thu, 1 Mar 2018 01:27:56 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Feb 2018 22:27:56 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,407,1515484800"; d="scan'208";a="33761289" Received: from aaronlu.sh.intel.com ([10.239.159.135]) by fmsmga004.fm.intel.com with ESMTP; 28 Feb 2018 22:27:54 -0800 From: Aaron Lu To: linux-mm@kvack.org, linux-kernel@vger.kernel.org Cc: Andrew Morton , Huang Ying , Dave Hansen , Kemi Wang , Tim Chen , Andi Kleen , Michal Hocko , Vlastimil Babka , Mel Gorman , Matthew Wilcox , David Rientjes Subject: [PATCH v4 3/3] mm/free_pcppages_bulk: prefetch buddy while not holding lock Date: Thu, 1 Mar 2018 14:28:45 +0800 Message-Id: <20180301062845.26038-4-aaron.lu@intel.com> X-Mailer: git-send-email 2.14.3 In-Reply-To: <20180301062845.26038-1-aaron.lu@intel.com> References: <20180301062845.26038-1-aaron.lu@intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When a page is freed back to the global pool, its buddy will be checked to see if it's possible to do a merge. This requires accessing buddy's page structure and that access could take a long time if it's cache cold. This patch adds a prefetch to the to-be-freed page's buddy outside of zone->lock in hope of accessing buddy's page structure later under zone->lock will be faster. Since we *always* do buddy merging and check an order-0 page's buddy to try to merge it when it goes into the main allocator, the cacheline will always come in, i.e. the prefetched data will never be unused. In the meantime, there are two concerns: 1 the prefetch could potentially evict existing cachelines, especially for L1D cache since it is not huge; 2 there is some additional instruction overhead, namely calculating buddy pfn twice. For 1, it's hard to say, this microbenchmark though shows good result but the actual benefit of this patch will be workload/CPU dependant; For 2, since the calculation is a XOR on two local variables, it's expected in many cases that cycles spent will be offset by reduced memory latency later. This is especially true for NUMA machines where multiple CPUs are contending on zone->lock and the most time consuming part under zone->lock is the wait of 'struct page' cacheline of the to-be-freed pages and their buddies. Test with will-it-scale/page_fault1 full load: kernel Broadwell(2S) Skylake(2S) Broadwell(4S) Skylake(4S) v4.16-rc2+ 9034215 7971818 13667135 15677465 patch2/3 9536374 +5.6% 8314710 +4.3% 14070408 +3.0% 16675866 +6.4% this patch 10338868 +8.4% 8544477 +2.8% 14839808 +5.5% 17155464 +2.9% Note: this patch's performance improvement percent is against patch2/3. [changelog stole from Dave Hansen and Mel Gorman's comments] https://lkml.org/lkml/2018/1/24/551 Suggested-by: Ying Huang Signed-off-by: Aaron Lu --- mm/page_alloc.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/mm/page_alloc.c b/mm/page_alloc.c index dafdcdec9c1f..1d838041931e 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -1141,6 +1141,9 @@ static void free_pcppages_bulk(struct zone *zone, int count, batch_free = count; do { + unsigned long pfn, buddy_pfn; + struct page *buddy; + page = list_last_entry(list, struct page, lru); /* must delete to avoid corrupting pcp list */ list_del(&page->lru); @@ -1150,6 +1153,18 @@ static void free_pcppages_bulk(struct zone *zone, int count, continue; list_add_tail(&page->lru, &head); + + /* + * We are going to put the page back to the global + * pool, prefetch its buddy to speed up later access + * under zone->lock. It is believed the overhead of + * calculating buddy_pfn here can be offset by reduced + * memory latency later. + */ + pfn = page_to_pfn(page); + buddy_pfn = __find_buddy_pfn(pfn, 0); + buddy = page + (buddy_pfn - pfn); + prefetch(buddy); } while (--count && --batch_free && !list_empty(list)); } -- 2.14.3