[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170328165803.podjvgo5zim44gip@node.shutemov.name>
Date: Tue, 28 Mar 2017 19:58:03 +0300
From: "Kirill A. Shutemov" <kirill@...temov.name>
To: Davidlohr Bueso <dave@...olabs.net>
Cc: Laurent Dufour <ldufour@...ux.vnet.ibm.com>, mingo@...nel.org,
peterz@...radead.org, akpm@...ux-foundation.org, jack@...e.cz,
kirill.shutemov@...ux.intel.com, mhocko@...e.com,
mgorman@...hsingularity.net, linux-kernel@...r.kernel.org,
Davidlohr Bueso <dbueso@...e.de>
Subject: Re: [PATCH 1/5] locking: Introduce range reader/writer lock
On Tue, Mar 28, 2017 at 09:39:18AM -0700, Davidlohr Bueso wrote:
> I'll wait to see if there are any more concerns and send a v2 with your corrections.
Have you tried drop-in replacement of mmap_sem with full range lock?
It would be interesting to see performance implication for this.
--
Kirill A. Shutemov
Powered by blists - more mailing lists