From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S946432AbdDTOjn (ORCPT ); Thu, 20 Apr 2017 10:39:43 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:54635 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S941847AbdDTOjk (ORCPT ); Thu, 20 Apr 2017 10:39:40 -0400 Subject: Re: [RFC 0/4] Replace mmap_sem by a range lock To: Matthew Wilcox References: <20170420133338.GC27790@bombadil.infradead.org> Cc: linux-mm@kvack.org, Davidlohr Bueso , akpm@linux-foundation.org, Jan Kara , "Kirill A . Shutemov" , Michal Hocko , Peter Zijlstra , Mel Gorman , haren@linux.vnet.ibm.com, aneesh.kumar@linux.vnet.ibm.com, khandual@linux.vnet.ibm.com, Paul.McKenney@us.ibm.com, linux-kernel@vger.kernel.org From: Laurent Dufour Date: Thu, 20 Apr 2017 16:39:32 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170420133338.GC27790@bombadil.infradead.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 17042014-0008-0000-0000-0000042C4A37 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17042014-0009-0000-0000-00001D5602BC Message-Id: <87628c87-d320-87e7-5076-b26432a72a0f@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-04-20_13:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=3 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1704200117 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/04/2017 15:33, Matthew Wilcox wrote: > On Wed, Apr 19, 2017 at 02:18:23PM +0200, Laurent Dufour wrote: >> Following the series pushed by Davidlohr Bueso based on the Jan Kara's >> work [1] which introduces range locks, this series implements the >> first step of the attempt to replace the mmap_sem by a range lock. > > Have you previously documented attempts to replace the mmap_sem by an > existing lock type before introducing a new (and frankly weird) lock? No :/ > My initial question is "Why not use RCU for this?" -- the rxrpc code > uses an rbtree protected by RCU. I'm also working on forward-porting work done by Peter Zijlstra : https://marc.info/?l=linux-mm&m=141384492326748 I'll send a series on top 4.10 soon.