Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755426AbdC1Q61 (ORCPT ); Tue, 28 Mar 2017 12:58:27 -0400 Received: from mail-wm0-f44.google.com ([74.125.82.44]:37101 "EHLO mail-wm0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753426AbdC1Q6Z (ORCPT ); Tue, 28 Mar 2017 12:58:25 -0400 Date: Tue, 28 Mar 2017 19:58:03 +0300 From: "Kirill A. Shutemov" To: Davidlohr Bueso Cc: Laurent Dufour , mingo@kernel.org, peterz@infradead.org, akpm@linux-foundation.org, jack@suse.cz, kirill.shutemov@linux.intel.com, mhocko@suse.com, mgorman@techsingularity.net, linux-kernel@vger.kernel.org, Davidlohr Bueso Subject: Re: [PATCH 1/5] locking: Introduce range reader/writer lock Message-ID: <20170328165803.podjvgo5zim44gip@node.shutemov.name> References: <1488863010-13028-1-git-send-email-dave@stgolabs.net> <1488863010-13028-2-git-send-email-dave@stgolabs.net> <2f7628f4-58e1-22c4-ccbe-3106c15cb405@linux.vnet.ibm.com> <20170328163918.GA27446@linux-80c1.suse> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170328163918.GA27446@linux-80c1.suse> User-Agent: NeoMutt/20170306 (1.8.0) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 312 Lines: 8 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