Re: [PATCH 02/34] mm, vmscan: move lru_lock to the node

2016-07-13 Thread Vlastimil Babka
On 07/13/2016 07:50 AM, Balbir Singh wrote: On Tue, Jul 12, 2016 at 12:18:05PM +0100, Mel Gorman wrote: On Tue, Jul 12, 2016 at 09:06:04PM +1000, Balbir Singh wrote: diff --git a/Documentation/cgroup-v1/memory.txt b/Documentation/cgroup-v1/memory.txt index b14abf217239..946e69103cdd 100644 ---

Re: [PATCH 02/34] mm, vmscan: move lru_lock to the node

2016-07-12 Thread Balbir Singh
On Tue, Jul 12, 2016 at 12:18:05PM +0100, Mel Gorman wrote: > On Tue, Jul 12, 2016 at 09:06:04PM +1000, Balbir Singh wrote: > > > diff --git a/Documentation/cgroup-v1/memory.txt > > > b/Documentation/cgroup-v1/memory.txt > > > index b14abf217239..946e69103cdd 100644 > > > --- a/Documentation/cgrou

Re: [PATCH 02/34] mm, vmscan: move lru_lock to the node

2016-07-12 Thread Mel Gorman
On Tue, Jul 12, 2016 at 09:06:04PM +1000, Balbir Singh wrote: > > diff --git a/Documentation/cgroup-v1/memory.txt > > b/Documentation/cgroup-v1/memory.txt > > index b14abf217239..946e69103cdd 100644 > > --- a/Documentation/cgroup-v1/memory.txt > > +++ b/Documentation/cgroup-v1/memory.txt > > @@ -2

Re: [PATCH 02/34] mm, vmscan: move lru_lock to the node

2016-07-12 Thread Balbir Singh
On Fri, Jul 08, 2016 at 10:34:38AM +0100, Mel Gorman wrote: > Node-based reclaim requires node-based LRUs and locking. This is a > preparation patch that just moves the lru_lock to the node so later > patches are easier to review. It is a mechanical change but note this > patch makes contention w