Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1445606

Re: [PATCH 2/3] mm, vmscan: Release/reacquire lru_lock on pgdat change

From Johannes Weiner <hannes@cmpxchg.org>
Newsgroups linux.kernel
Subject Re: [PATCH 2/3] mm, vmscan: Release/reacquire lru_lock on pgdat change
Date 2016-07-18 18:20 +0200
Message-ID <rWjqV-8vS-1@gated-at.bofh.it> (permalink)
References <rWibv-7xJ-13@gated-at.bofh.it> <rWibv-7xJ-21@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Mon, Jul 18, 2016 at 03:50:25PM +0100, Mel Gorman wrote:
> With node-lru, the locking is based on the pgdat. As Minchan pointed
> out, there is an opportunity to reduce LRU lock release/acquire in
> check_move_unevictable_pages by only changing lock on a pgdat change.
> 
> Signed-off-by: Mel Gorman <mgorman@techsingularity.net>

Acked-by: Johannes Weiner <hannes@cmpxchg.org>

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH 2/3] mm, vmscan: Release/reacquire lru_lock on pgdat change Mel Gorman <mgorman@techsingularity.net> - 2016-07-18 17:00 +0200
  Re: [PATCH 2/3] mm, vmscan: Release/reacquire lru_lock on pgdat  change Johannes Weiner <hannes@cmpxchg.org> - 2016-07-18 18:20 +0200
  Re: [PATCH 2/3] mm, vmscan: Release/reacquire lru_lock on pgdat  change Minchan Kim <minchan@kernel.org> - 2016-07-19 02:00 +0200

csiph-web