[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180208153652.481a77e57cc32c9e1a7e4269@linux-foundation.org>
Date: Thu, 8 Feb 2018 15:36:52 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: daniel.m.jordan@...cle.com
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
aaron.lu@...el.com, ak@...ux.intel.com, Dave.Dice@...cle.com,
dave@...olabs.net, khandual@...ux.vnet.ibm.com,
ldufour@...ux.vnet.ibm.com, mgorman@...e.de, mhocko@...nel.org,
pasha.tatashin@...cle.com, steven.sistare@...cle.com,
yossi.lev@...cle.com
Subject: Re: [RFC PATCH v1 00/13] lru_lock scalability
On Wed, 31 Jan 2018 18:04:00 -0500 daniel.m.jordan@...cle.com wrote:
> lru_lock, a per-node* spinlock that protects an LRU list, is one of the
> hottest locks in the kernel. On some workloads on large machines, it
> shows up at the top of lock_stat.
Do you have details on which callsites are causing the problem? That
would permit us to consider other approaches, perhaps.
Powered by blists - more mailing lists