[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aa14d724-525c-7532-2e8e-6c4c6094e03f@intel.com>
Date: Fri, 2 Mar 2018 07:34:01 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Aaron Lu <aaron.lu@...el.com>, Michal Hocko <mhocko@...nel.org>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Huang Ying <ying.huang@...el.com>,
Kemi Wang <kemi.wang@...el.com>,
Tim Chen <tim.c.chen@...ux.intel.com>,
Andi Kleen <ak@...ux.intel.com>,
Vlastimil Babka <vbabka@...e.cz>,
Mel Gorman <mgorman@...hsingularity.net>,
Matthew Wilcox <willy@...radead.org>,
David Rientjes <rientjes@...gle.com>
Subject: Re: [PATCH v4 2/3] mm/free_pcppages_bulk: do not hold lock when
picking pages to free
On 03/01/2018 11:15 PM, Aaron Lu wrote:
>
>> I am still quite surprised that this would have such a large impact.
> Most likely due to the cachelines for these page structures are warmed
> up outside of zone->lock.
The workload here is a pretty tight microbenchmark and single biggest
bottleneck is cache misses on 'struct page'. It's not memory bandwidth
bound. So, anything you can give the CPU keep it fed and not waiting on
cache misses will be a win.
There's never going to be a real-world workload that sees this kind of
increase, but the change in the micro isn't super-surprising because it
so directly targets the bottleneck.
Powered by blists - more mailing lists