From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@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>,
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 4/4] Change mmap_sem to range lock
Date: Thu, 20 Apr 2017 16:42:39 +0200 [thread overview]
Message-ID: <cb1c8fbb-8d1a-845a-2fdc-dfdb25b92bae@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170420143736.mvj6bpwsr4w3fjwk@hirez.programming.kicks-ass.net>
On 20/04/2017 16:37, Peter Zijlstra wrote:
> On Thu, Apr 20, 2017 at 04:28:20PM +0200, Laurent Dufour wrote:
>> [resent this patch which seems to have not reached the mailing lists]
>
> Probably because its too big at ~180k ?
Probably, but this time it has reached linux-mm ... at least.
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@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>,
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 4/4] Change mmap_sem to range lock
Date: Thu, 20 Apr 2017 16:42:39 +0200 [thread overview]
Message-ID: <cb1c8fbb-8d1a-845a-2fdc-dfdb25b92bae@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170420143736.mvj6bpwsr4w3fjwk@hirez.programming.kicks-ass.net>
On 20/04/2017 16:37, Peter Zijlstra wrote:
> On Thu, Apr 20, 2017 at 04:28:20PM +0200, Laurent Dufour wrote:
>> [resent this patch which seems to have not reached the mailing lists]
>
> Probably because its too big at ~180k ?
Probably, but this time it has reached linux-mm ... at least.
--
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:42 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
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 [this message]
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=cb1c8fbb-8d1a-845a-2fdc-dfdb25b92bae@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 \
/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.