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;
Date:   Thu, 8 Feb 2018 15:36:52 -0800
From:   Andrew Morton <akpm@linux-foundation.org>
To:     daniel.m.jordan@oracle.com
Cc:     linux-mm@kvack.org, linux-kernel@vger.kernel.org,
        aaron.lu@intel.com, ak@linux.intel.com, Dave.Dice@oracle.com,
        dave@stgolabs.net, khandual@linux.vnet.ibm.com,
        ldufour@linux.vnet.ibm.com, mgorman@suse.de, mhocko@kernel.org,
        pasha.tatashin@oracle.com, steven.sistare@oracle.com,
        yossi.lev@oracle.com
Subject: Re: [RFC PATCH v1 00/13] lru_lock scalability
Message-Id: <20180208153652.481a77e57cc32c9e1a7e4269@linux-foundation.org>
In-Reply-To: <20180131230413.27653-1-daniel.m.jordan@oracle.com>
References: <20180131230413.27653-1-daniel.m.jordan@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, 31 Jan 2018 18:04:00 -0500 daniel.m.jordan@oracle.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.