From: Steven Whitehouse <swhiteho@redhat.com>
To: daniel.m.jordan@oracle.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Cc: aaron.lu@intel.com, ak@linux.intel.com,
akpm@linux-foundation.org, 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
Date: Thu, 1 Feb 2018 15:54:38 +0000 [thread overview]
Message-ID: <6bd1c8a5-c682-a3ce-1f9f-f1f53b4117a9@redhat.com> (raw)
In-Reply-To: <20180131230413.27653-1-daniel.m.jordan@oracle.com>
Hi,
On 31/01/18 23:04, 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.
>
> One way to improve lru_lock scalability is to introduce an array of locks,
> with each lock protecting certain batches of LRU pages.
>
> *ooooooooooo**ooooooooooo**ooooooooooo**oooo ...
> | || || ||
> \ batch 1 / \ batch 2 / \ batch 3 /
>
> In this ASCII depiction of an LRU, a page is represented with either '*'
> or 'o'. An asterisk indicates a sentinel page, which is a page at the
> edge of a batch. An 'o' indicates a non-sentinel page.
>
> To remove a non-sentinel LRU page, only one lock from the array is
> required. This allows multiple threads to remove pages from different
> batches simultaneously. A sentinel page requires lru_lock in addition to
> a lock from the array.
>
> Full performance numbers appear in the last patch in this series, but this
> prototype allows a microbenchmark to do up to 28% more page faults per
> second with 16 or more concurrent processes.
>
> This work was developed in collaboration with Steve Sistare.
>
> Note: This is an early prototype. I'm submitting it now to support my
> request to attend LSF/MM, as well as get early feedback on the idea. Any
> comments appreciated.
>
>
> * lru_lock is actually per-memcg, but without memcg's in the picture it
> becomes per-node.
GFS2 has an lru list for glocks, which can be contended under certain
workloads. Work is still ongoing to figure out exactly why, but this
looks like it might be a good approach to that issue too. The main
purpose of GFS2's lru list is to allow shrinking of the glocks under
memory pressure via the gfs2_scan_glock_lru() function, and it looks
like this type of approach could be used there to improve the scalability,
Steve.
>
> Aaron Lu (1):
> mm: add a percpu_pagelist_batch sysctl interface
>
> Daniel Jordan (12):
> mm: allow compaction to be disabled
> mm: add lock array to pgdat and batch fields to struct page
> mm: introduce struct lru_list_head in lruvec to hold per-LRU batch
> info
> mm: add batching logic to add/delete/move API's
> mm: add lru_[un]lock_all APIs
> mm: convert to-be-refactored lru_lock callsites to lock-all API
> mm: temporarily convert lru_lock callsites to lock-all API
> mm: introduce add-only version of pagevec_lru_move_fn
> mm: add LRU batch lock API's
> mm: use lru_batch locking in release_pages
> mm: split up release_pages into non-sentinel and sentinel passes
> mm: splice local lists onto the front of the LRU
>
> include/linux/mm_inline.h | 209 +++++++++++++++++++++++++++++++++++++++++++++-
> include/linux/mm_types.h | 5 ++
> include/linux/mmzone.h | 25 +++++-
> kernel/sysctl.c | 9 ++
> mm/Kconfig | 1 -
> mm/huge_memory.c | 6 +-
> mm/memcontrol.c | 5 +-
> mm/mlock.c | 11 +--
> mm/mmzone.c | 7 +-
> mm/page_alloc.c | 43 +++++++++-
> mm/page_idle.c | 4 +-
> mm/swap.c | 208 ++++++++++++++++++++++++++++++++++++---------
> mm/vmscan.c | 49 +++++------
> 13 files changed, 500 insertions(+), 82 deletions(-)
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-02-01 15:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 23:04 [RFC PATCH v1 00/13] lru_lock scalability daniel.m.jordan
2018-01-31 23:04 ` [RFC PATCH v1 01/13] mm: add a percpu_pagelist_batch sysctl interface daniel.m.jordan
2018-01-31 23:04 ` [RFC PATCH v1 02/13] mm: allow compaction to be disabled daniel.m.jordan
2018-01-31 23:04 ` [RFC PATCH v1 03/13] mm: add lock array to pgdat and batch fields to struct page daniel.m.jordan
2018-02-01 22:50 ` Tim Chen
2018-02-02 4:29 ` Daniel Jordan
2018-01-31 23:04 ` [RFC PATCH v1 04/13] mm: introduce struct lru_list_head in lruvec to hold per-LRU batch info daniel.m.jordan
2018-01-31 23:04 ` [RFC PATCH v1 05/13] mm: add batching logic to add/delete/move API's daniel.m.jordan
2018-01-31 23:04 ` [RFC PATCH v1 06/13] mm: add lru_[un]lock_all APIs daniel.m.jordan
2018-01-31 23:04 ` [RFC PATCH v1 07/13] mm: convert to-be-refactored lru_lock callsites to lock-all API daniel.m.jordan
2018-01-31 23:04 ` [RFC PATCH v1 08/13] mm: temporarily convert " daniel.m.jordan
2018-01-31 23:04 ` [RFC PATCH v1 09/13] mm: introduce add-only version of pagevec_lru_move_fn daniel.m.jordan
2018-01-31 23:04 ` [RFC PATCH v1 10/13] mm: add LRU batch lock API's daniel.m.jordan
2018-01-31 23:04 ` [RFC PATCH v1 11/13] mm: use lru_batch locking in release_pages daniel.m.jordan
2018-01-31 23:04 ` [RFC PATCH v1 12/13] mm: split up release_pages into non-sentinel and sentinel passes daniel.m.jordan
2018-02-02 14:40 ` Laurent Dufour
2018-02-02 17:00 ` Laurent Dufour
2018-02-06 17:47 ` Daniel Jordan
2018-02-05 4:58 ` [lkp-robot] [mm] 44b163e12f: kernel_BUG_at_mm/swap.c kernel test robot
2018-01-31 23:04 ` [RFC PATCH v1 13/13] mm: splice local lists onto the front of the LRU daniel.m.jordan
2018-02-01 23:30 ` Tim Chen
2018-02-02 5:17 ` Daniel Jordan
2018-02-02 5:21 ` Aaron Lu
2018-02-06 17:38 ` Daniel Jordan
2018-02-02 15:22 ` Laurent Dufour
2018-02-06 18:18 ` Daniel Jordan
2018-02-01 15:54 ` Steven Whitehouse [this message]
2018-02-02 4:18 ` [RFC PATCH v1 00/13] lru_lock scalability Daniel Jordan
2018-02-02 10:50 ` Steven Whitehouse
2018-02-08 23:36 ` Andrew Morton
2018-02-13 21:07 ` Daniel Jordan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6bd1c8a5-c682-a3ce-1f9f-f1f53b4117a9@redhat.com \
--to=swhiteho@redhat.com \
--cc=Dave.Dice@oracle.com \
--cc=aaron.lu@intel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.m.jordan@oracle.com \
--cc=dave@stgolabs.net \
--cc=khandual@linux.vnet.ibm.com \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=pasha.tatashin@oracle.com \
--cc=steven.sistare@oracle.com \
--cc=yossi.lev@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).