Re: [PATCH 0/3] mm,vdso: preallocate new vmas

2013-11-04 Thread Davidlohr Bueso
Hi Andrew - On Thu, 2013-10-17 at 17:50 -0700, Davidlohr Bueso wrote: > Linus recently pointed out[1] some of the amount of unnecessary work > being done with the mmap_sem held. This patchset is a very initial > approach on reducing some of the contention on this lock, and moving > work outside

Re: [PATCH 0/3] mm,vdso: preallocate new vmas

2013-10-23 Thread Andy Lutomirski
On Wed, Oct 23, 2013 at 3:13 AM, Michel Lespinasse wrote: > On Tue, Oct 22, 2013 at 10:54 AM, Andy Lutomirski wrote: >> On 10/22/2013 08:48 AM, wal...@google.com wrote: >>> Generally the problems I see with mmap_sem are related to long latency >>> operations. Specifically, the mmap_sem write side

Re: [PATCH 0/3] mm,vdso: preallocate new vmas

2013-10-23 Thread Michel Lespinasse
On Tue, Oct 22, 2013 at 10:54 AM, Andy Lutomirski wrote: > On 10/22/2013 08:48 AM, wal...@google.com wrote: >> Generally the problems I see with mmap_sem are related to long latency >> operations. Specifically, the mmap_sem write side is currently held >> during the entire munmap operation, which

Re: [PATCH 0/3] mm,vdso: preallocate new vmas

2013-10-22 Thread Davidlohr Bueso
On Tue, 2013-10-22 at 08:48 -0700, wal...@google.com wrote: > On Thu, Oct 17, 2013 at 05:50:35PM -0700, Davidlohr Bueso wrote: > > Linus recently pointed out[1] some of the amount of unnecessary work > > being done with the mmap_sem held. This patchset is a very initial > > approach on reducing s

Re: [PATCH 0/3] mm,vdso: preallocate new vmas

2013-10-22 Thread Andy Lutomirski
On 10/22/2013 08:48 AM, wal...@google.com wrote: > On Thu, Oct 17, 2013 at 05:50:35PM -0700, Davidlohr Bueso wrote: >> Linus recently pointed out[1] some of the amount of unnecessary work >> being done with the mmap_sem held. This patchset is a very initial >> approach on reducing some of the con

Re: [PATCH 0/3] mm,vdso: preallocate new vmas

2013-10-22 Thread Michel Lespinasse
On Tue, Oct 22, 2013 at 9:20 AM, Linus Torvalds wrote: > On Tue, Oct 22, 2013 at 4:48 PM, wrote: >> Generally the problems I see with mmap_sem are related to long latency >> operations. Specifically, the mmap_sem write side is currently held >> during the entire munmap operation, which iterates

Re: [PATCH 0/3] mm,vdso: preallocate new vmas

2013-10-22 Thread Linus Torvalds
On Tue, Oct 22, 2013 at 4:48 PM, wrote: > > Generally the problems I see with mmap_sem are related to long latency > operations. Specifically, the mmap_sem write side is currently held > during the entire munmap operation, which iterates over user pages to > free them, and can take hundreds of m

Re: [PATCH 0/3] mm,vdso: preallocate new vmas

2013-10-22 Thread walken
On Thu, Oct 17, 2013 at 05:50:35PM -0700, Davidlohr Bueso wrote: > Linus recently pointed out[1] some of the amount of unnecessary work > being done with the mmap_sem held. This patchset is a very initial > approach on reducing some of the contention on this lock, and moving > work outside of the

[PATCH 0/3] mm,vdso: preallocate new vmas

2013-10-17 Thread Davidlohr Bueso
Linus recently pointed out[1] some of the amount of unnecessary work being done with the mmap_sem held. This patchset is a very initial approach on reducing some of the contention on this lock, and moving work outside of the critical region. Patch 1 adds a simple helper function. Patch 2 moves