From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, Davidlohr Bueso <dave@stgolabs.net>,
akpm@linux-foundation.org, Jan Kara <jack@suse.cz>,
"Kirill A . Shutemov" <kirill@shutemov.name>,
Michal Hocko <mhocko@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Mel Gorman <mgorman@techsingularity.net>,
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
Subject: Re: [RFC 0/4] Replace mmap_sem by a range lock
Date: Thu, 20 Apr 2017 16:39:32 +0200 [thread overview]
Message-ID: <87628c87-d320-87e7-5076-b26432a72a0f@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170420133338.GC27790@bombadil.infradead.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.
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, Davidlohr Bueso <dave@stgolabs.net>,
akpm@linux-foundation.org, Jan Kara <jack@suse.cz>,
"Kirill A . Shutemov" <kirill@shutemov.name>,
Michal Hocko <mhocko@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Mel Gorman <mgorman@techsingularity.net>,
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
Subject: Re: [RFC 0/4] Replace mmap_sem by a range lock
Date: Thu, 20 Apr 2017 16:39:32 +0200 [thread overview]
Message-ID: <87628c87-d320-87e7-5076-b26432a72a0f@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170420133338.GC27790@bombadil.infradead.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.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-04-20 14:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 12:18 [RFC 0/4] Replace mmap_sem by a range lock Laurent Dufour
2017-04-19 12:18 ` Laurent Dufour
2017-04-19 12:18 ` [RFC 1/4] Add additional range parameter to GUP() and handle_page_fault() Laurent Dufour
2017-04-19 12:18 ` Laurent Dufour
2017-04-19 12:18 ` [RFC 2/4] Deactivate mmap_sem assert Laurent Dufour
2017-04-19 12:18 ` Laurent Dufour
2017-04-19 12:30 ` Peter Zijlstra
2017-04-19 12:30 ` Peter Zijlstra
2017-04-19 13:45 ` Laurent Dufour
2017-04-19 13:45 ` Laurent Dufour
2017-04-19 13:54 ` Peter Zijlstra
2017-04-19 13:54 ` Peter Zijlstra
2017-04-19 12:18 ` [RFC 3/4] Remove nest locking operation with mmap_sem Laurent Dufour
2017-04-19 12:18 ` Laurent Dufour
2017-04-19 12:18 ` [RFC 4/4] Change mmap_sem to range lock Laurent Dufour
2017-04-20 13:33 ` [RFC 0/4] Replace mmap_sem by a " Matthew Wilcox
2017-04-20 13:33 ` Matthew Wilcox
2017-04-20 14:39 ` Laurent Dufour [this message]
2017-04-20 14:39 ` Laurent Dufour
2017-04-20 14:28 ` [RFC 4/4] Change mmap_sem to " Laurent Dufour
2017-04-20 14:28 ` Laurent Dufour
2017-04-20 14:37 ` Peter Zijlstra
2017-04-20 14:37 ` Peter Zijlstra
2017-04-20 14:42 ` Laurent Dufour
2017-04-20 14:42 ` Laurent Dufour
2017-04-20 23:36 ` Andi Kleen
2017-04-20 23:36 ` Andi Kleen
2017-04-24 15:47 ` Laurent Dufour
2017-04-24 15:47 ` Laurent Dufour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87628c87-d320-87e7-5076-b26432a72a0f@linux.vnet.ibm.com \
--to=ldufour@linux.vnet.ibm.com \
--cc=Paul.McKenney@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dave@stgolabs.net \
--cc=haren@linux.vnet.ibm.com \
--cc=jack@suse.cz \
--cc=khandual@linux.vnet.ibm.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=peterz@infradead.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.