From: Vlastimil Babka <vbabka@suse.cz>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Michel Lespinasse <michel@lespinasse.org>,
Jerome Glisse <jglisse@google.com>,
Michal Hocko <mhocko@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>, Davidlohr Bueso <dave@stgolabs.net>,
Matthew Wilcox <willy@infradead.org>,
"Liam R. Howlett" <liam.howlett@oracle.com>,
Peter Zijlstra <peterz@infradead.org>,
Laurent Dufour <ldufour@linux.ibm.com>,
Laurent Dufour <laurent.dufour@fr.ibm.com>,
"Paul E . McKenney" <paulmck@kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Song Liu <songliubraving@fb.com>, Peter Xu <peterx@redhat.com>,
David Hildenbrand <david@redhat.com>,
dhowells@redhat.com, Hugh Dickins <hughd@google.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
David Rientjes <rientjes@google.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Joel Fernandes <joelaf@google.com>,
Minchan Kim <minchan@google.com>,
kernel-team <kernel-team@android.com>,
linux-mm <linux-mm@kvack.org>,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH RESEND 00/28] per-VMA locks proposal
Date: Thu, 29 Sep 2022 13:18:25 +0200 [thread overview]
Message-ID: <621612d7-c537-3971-9520-a3dec7b43cb4@suse.cz> (raw)
In-Reply-To: <CAJuCfpEcTv5crNumhMTCf2yAJ5+86ph78-B+eyk_N84Ce=nr5w@mail.gmail.com>
On 9/28/22 04:28, Suren Baghdasaryan wrote:
> On Sun, Sep 11, 2022 at 2:35 AM Vlastimil Babka <vbabka@suse.cz> wrote:
>>
>> On 9/2/22 01:26, Suren Baghdasaryan wrote:
>> >
>> >>
>> >> Two complaints so far:
>> >> - I don't like the vma_mark_locked() name. To me it says that the caller
>> >> already took or is taking the lock and this function is just marking that
>> >> we're holding the lock, but it's really taking a different type of lock. But
>> >> this function can block, it really is taking a lock, so it should say that.
>> >>
>> >> This is AFAIK a new concept, not sure I'm going to have anything good either,
>> >> but perhaps vma_lock_multiple()?
>> >
>> > I'm open to name suggestions but vma_lock_multiple() is a bit
>> > confusing to me. Will wait for more suggestions.
>>
>> Well, it does act like a vma_write_lock(), no? So why not that name. The
>> checking function for it is even called vma_assert_write_locked().
>>
>> We just don't provide a single vma_write_unlock(), but a
>> vma_mark_unlocked_all(), that could be instead named e.g.
>> vma_write_unlock_all().
>> But it's called on a mm, so maybe e.g. mm_vma_write_unlock_all()?
>
> Thank you for your suggestions, Vlastimil! vma_write_lock() sounds
> good to me. For vma_mark_unlocked_all() replacement, I would prefer
> vma_write_unlock_all() which keeps the vma_write_XXX naming pattern to
OK.
> indicate that these are operating on the same locks. If the fact that
> it accepts mm_struct as a parameter is an issue then maybe
> vma_write_unlock_mm() ?
Sounds good!
>>
>>
WARNING: multiple messages have this Message-ID (diff)
From: Vlastimil Babka <vbabka@suse.cz>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Michel Lespinasse <michel@lespinasse.org>,
Joel Fernandes <joelaf@google.com>,
Song Liu <songliubraving@fb.com>, Michal Hocko <mhocko@suse.com>,
David Hildenbrand <david@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Peter Xu <peterx@redhat.com>,
dhowells@redhat.com, linux-mm <linux-mm@kvack.org>,
Jerome Glisse <jglisse@google.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Minchan Kim <minchan@google.com>,
x86@kernel.org, Hugh Dickins <hughd@google.com>,
Matthew Wilcox <willy@infradead.org>,
Laurent Dufour <laurent.dufour@fr.ibm.com>,
Mel Gorman <mgorman@suse.de>,
David Rientjes <rientjes@google.com>,
Axel Rasmussen <axelrasmussen@google.com>,
kernel-team <kernel-team@android.com>,
"Paul E . McKenney" <paulmck@kernel.org>,
"Liam R. Howlett" <liam.howlett@oracle.com>,
Andy Lutomirski <luto@kernel.org>,
Laurent Dufour <ldufour@linux.ibm.com>,
linux-arm-kernel@lists.infradead.org,
Kent Overstreet <kent.overstreet@linux.dev>,
LKML < linux-kernel@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH RESEND 00/28] per-VMA locks proposal
Date: Thu, 29 Sep 2022 13:18:25 +0200 [thread overview]
Message-ID: <621612d7-c537-3971-9520-a3dec7b43cb4@suse.cz> (raw)
In-Reply-To: <CAJuCfpEcTv5crNumhMTCf2yAJ5+86ph78-B+eyk_N84Ce=nr5w@mail.gmail.com>
On 9/28/22 04:28, Suren Baghdasaryan wrote:
> On Sun, Sep 11, 2022 at 2:35 AM Vlastimil Babka <vbabka@suse.cz> wrote:
>>
>> On 9/2/22 01:26, Suren Baghdasaryan wrote:
>> >
>> >>
>> >> Two complaints so far:
>> >> - I don't like the vma_mark_locked() name. To me it says that the caller
>> >> already took or is taking the lock and this function is just marking that
>> >> we're holding the lock, but it's really taking a different type of lock. But
>> >> this function can block, it really is taking a lock, so it should say that.
>> >>
>> >> This is AFAIK a new concept, not sure I'm going to have anything good either,
>> >> but perhaps vma_lock_multiple()?
>> >
>> > I'm open to name suggestions but vma_lock_multiple() is a bit
>> > confusing to me. Will wait for more suggestions.
>>
>> Well, it does act like a vma_write_lock(), no? So why not that name. The
>> checking function for it is even called vma_assert_write_locked().
>>
>> We just don't provide a single vma_write_unlock(), but a
>> vma_mark_unlocked_all(), that could be instead named e.g.
>> vma_write_unlock_all().
>> But it's called on a mm, so maybe e.g. mm_vma_write_unlock_all()?
>
> Thank you for your suggestions, Vlastimil! vma_write_lock() sounds
> good to me. For vma_mark_unlocked_all() replacement, I would prefer
> vma_write_unlock_all() which keeps the vma_write_XXX naming pattern to
OK.
> indicate that these are operating on the same locks. If the fact that
> it accepts mm_struct as a parameter is an issue then maybe
> vma_write_unlock_mm() ?
Sounds good!
>>
>>
WARNING: multiple messages have this Message-ID (diff)
From: Vlastimil Babka <vbabka@suse.cz>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Michel Lespinasse <michel@lespinasse.org>,
Jerome Glisse <jglisse@google.com>,
Michal Hocko <mhocko@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>, Davidlohr Bueso <dave@stgolabs.net>,
Matthew Wilcox <willy@infradead.org>,
"Liam R. Howlett" <liam.howlett@oracle.com>,
Peter Zijlstra <peterz@infradead.org>,
Laurent Dufour <ldufour@linux.ibm.com>,
Laurent Dufour <laurent.dufour@fr.ibm.com>,
"Paul E . McKenney" <paulmck@kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Song Liu <songliubraving@fb.com>, Peter Xu <peterx@redhat.com>,
David Hildenbrand <david@redhat.com>,
dhowells@redhat.com, Hugh Dickins <hughd@google.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
David Rientjes <rientjes@google.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Joel Fernandes <joelaf@google.com>,
Minchan Kim <minchan@google.com>,
kernel-team <kernel-team@android.com>,
linux-mm <linux-mm@kvack.org>,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH RESEND 00/28] per-VMA locks proposal
Date: Thu, 29 Sep 2022 13:18:25 +0200 [thread overview]
Message-ID: <621612d7-c537-3971-9520-a3dec7b43cb4@suse.cz> (raw)
In-Reply-To: <CAJuCfpEcTv5crNumhMTCf2yAJ5+86ph78-B+eyk_N84Ce=nr5w@mail.gmail.com>
On 9/28/22 04:28, Suren Baghdasaryan wrote:
> On Sun, Sep 11, 2022 at 2:35 AM Vlastimil Babka <vbabka@suse.cz> wrote:
>>
>> On 9/2/22 01:26, Suren Baghdasaryan wrote:
>> >
>> >>
>> >> Two complaints so far:
>> >> - I don't like the vma_mark_locked() name. To me it says that the caller
>> >> already took or is taking the lock and this function is just marking that
>> >> we're holding the lock, but it's really taking a different type of lock. But
>> >> this function can block, it really is taking a lock, so it should say that.
>> >>
>> >> This is AFAIK a new concept, not sure I'm going to have anything good either,
>> >> but perhaps vma_lock_multiple()?
>> >
>> > I'm open to name suggestions but vma_lock_multiple() is a bit
>> > confusing to me. Will wait for more suggestions.
>>
>> Well, it does act like a vma_write_lock(), no? So why not that name. The
>> checking function for it is even called vma_assert_write_locked().
>>
>> We just don't provide a single vma_write_unlock(), but a
>> vma_mark_unlocked_all(), that could be instead named e.g.
>> vma_write_unlock_all().
>> But it's called on a mm, so maybe e.g. mm_vma_write_unlock_all()?
>
> Thank you for your suggestions, Vlastimil! vma_write_lock() sounds
> good to me. For vma_mark_unlocked_all() replacement, I would prefer
> vma_write_unlock_all() which keeps the vma_write_XXX naming pattern to
OK.
> indicate that these are operating on the same locks. If the fact that
> it accepts mm_struct as a parameter is an issue then maybe
> vma_write_unlock_mm() ?
Sounds good!
>>
>>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-29 11:18 UTC|newest]
Thread overview: 273+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 17:34 [RFC PATCH RESEND 00/28] per-VMA locks proposal Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 01/28] mm: introduce CONFIG_PER_VMA_LOCK Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 02/28] mm: rcu safe VMA freeing Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 03/28] mm: introduce __find_vma to be used without mmap_lock protection Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 20:22 ` Kent Overstreet
2022-09-01 20:22 ` Kent Overstreet
2022-09-01 20:22 ` Kent Overstreet
2022-09-01 23:18 ` Suren Baghdasaryan
2022-09-01 23:18 ` Suren Baghdasaryan
2022-09-01 23:18 ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 04/28] mm: move mmap_lock assert function definitions Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 20:24 ` Kent Overstreet
2022-09-01 20:24 ` Kent Overstreet
2022-09-01 20:24 ` Kent Overstreet
2022-09-01 20:51 ` Liam Howlett
2022-09-01 20:51 ` Liam Howlett
2022-09-01 20:51 ` Liam Howlett
2022-09-01 23:21 ` Suren Baghdasaryan
2022-09-01 23:21 ` Suren Baghdasaryan
2022-09-01 23:21 ` Suren Baghdasaryan
2022-09-02 6:23 ` Sebastian Andrzej Siewior
2022-09-02 6:23 ` Sebastian Andrzej Siewior
2022-09-02 6:23 ` Sebastian Andrzej Siewior
2022-09-02 17:46 ` Suren Baghdasaryan
2022-09-02 17:46 ` Suren Baghdasaryan
2022-09-02 17:46 ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 05/28] mm: add per-VMA lock and helper functions to control it Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-06 13:46 ` Laurent Dufour
2022-09-06 13:46 ` Laurent Dufour
2022-09-06 13:46 ` Laurent Dufour
2022-09-06 17:24 ` Suren Baghdasaryan
2022-09-06 17:24 ` Suren Baghdasaryan
2022-09-06 17:24 ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 06/28] mm: mark VMA as locked whenever vma->vm_flags are modified Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-06 14:26 ` Laurent Dufour
2022-09-06 14:26 ` Laurent Dufour
2022-09-06 14:26 ` Laurent Dufour
2022-09-06 19:00 ` Suren Baghdasaryan
2022-09-06 19:00 ` Suren Baghdasaryan
2022-09-06 19:00 ` Suren Baghdasaryan
2022-09-06 20:00 ` Liam Howlett
2022-09-06 20:00 ` Liam Howlett
2022-09-06 20:00 ` Liam Howlett
2022-09-06 20:13 ` Suren Baghdasaryan
2022-09-06 20:13 ` Suren Baghdasaryan
2022-09-06 20:13 ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 07/28] kernel/fork: mark VMAs as locked before copying pages during fork Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-06 14:37 ` Laurent Dufour
2022-09-06 14:37 ` Laurent Dufour
2022-09-06 14:37 ` Laurent Dufour
2022-09-08 23:57 ` Suren Baghdasaryan
2022-09-08 23:57 ` Suren Baghdasaryan
2022-09-08 23:57 ` Suren Baghdasaryan
2022-09-09 13:27 ` Laurent Dufour
2022-09-09 13:27 ` Laurent Dufour
2022-09-09 13:27 ` Laurent Dufour
2022-09-09 16:29 ` Suren Baghdasaryan
2022-09-09 16:29 ` Suren Baghdasaryan
2022-09-09 16:29 ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 08/28] mm/khugepaged: mark VMA as locked while collapsing a hugepage Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-06 14:43 ` Laurent Dufour
2022-09-06 14:43 ` Laurent Dufour
2022-09-06 14:43 ` Laurent Dufour
2022-09-09 0:15 ` Suren Baghdasaryan
2022-09-09 0:15 ` Suren Baghdasaryan
2022-09-09 0:15 ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 09/28] mm/mempolicy: mark VMA as locked when changing protection policy Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-06 14:47 ` Laurent Dufour
2022-09-06 14:47 ` Laurent Dufour
2022-09-06 14:47 ` Laurent Dufour
2022-09-09 0:27 ` Suren Baghdasaryan
2022-09-09 0:27 ` Suren Baghdasaryan
2022-09-09 0:27 ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 10/28] mm/mmap: mark VMAs as locked in vma_adjust Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-06 15:35 ` Laurent Dufour
2022-09-06 15:35 ` Laurent Dufour
2022-09-06 15:35 ` Laurent Dufour
2022-09-09 0:51 ` Suren Baghdasaryan
2022-09-09 0:51 ` Suren Baghdasaryan
2022-09-09 0:51 ` Suren Baghdasaryan
2022-09-09 15:52 ` Laurent Dufour
2022-09-09 15:52 ` Laurent Dufour
2022-09-09 15:52 ` Laurent Dufour
2022-09-01 17:34 ` [RFC PATCH RESEND 11/28] mm/mmap: mark VMAs as locked before merging or splitting them Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-06 15:44 ` Laurent Dufour
2022-09-06 15:44 ` Laurent Dufour
2022-09-06 15:44 ` Laurent Dufour
2022-09-01 17:35 ` [RFC PATCH RESEND 12/28] mm/mremap: mark VMA as locked while remapping it to a new address range Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-06 16:09 ` Laurent Dufour
2022-09-06 16:09 ` Laurent Dufour
2022-09-06 16:09 ` Laurent Dufour
2022-09-01 17:35 ` [RFC PATCH RESEND 13/28] mm: conditionally mark VMA as locked in free_pgtables and unmap_page_range Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-09 10:33 ` Laurent Dufour
2022-09-09 10:33 ` Laurent Dufour
2022-09-09 10:33 ` Laurent Dufour
2022-09-09 16:43 ` Suren Baghdasaryan
2022-09-09 16:43 ` Suren Baghdasaryan
2022-09-09 16:43 ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 14/28] mm: mark VMAs as locked before isolating them Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-09 13:35 ` Laurent Dufour
2022-09-09 13:35 ` Laurent Dufour
2022-09-09 13:35 ` Laurent Dufour
2022-09-09 16:28 ` Suren Baghdasaryan
2022-09-09 16:28 ` Suren Baghdasaryan
2022-09-09 16:28 ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 15/28] mm/mmap: mark adjacent VMAs as locked if they can grow into unmapped area Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-09 13:43 ` Laurent Dufour
2022-09-09 13:43 ` Laurent Dufour
2022-09-09 13:43 ` Laurent Dufour
2022-09-09 16:25 ` Suren Baghdasaryan
2022-09-09 16:25 ` Suren Baghdasaryan
2022-09-09 16:25 ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 16/28] kernel/fork: assert no VMA readers during its destruction Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-09 13:56 ` Laurent Dufour
2022-09-09 13:56 ` Laurent Dufour
2022-09-09 13:56 ` Laurent Dufour
2022-09-09 16:19 ` Suren Baghdasaryan
2022-09-09 16:19 ` Suren Baghdasaryan
2022-09-09 16:19 ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 17/28] mm/mmap: prevent pagefault handler from racing with mmu_notifier registration Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-09 14:20 ` Laurent Dufour
2022-09-09 14:20 ` Laurent Dufour
2022-09-09 14:20 ` Laurent Dufour
2022-09-09 16:12 ` Suren Baghdasaryan
2022-09-09 16:12 ` Suren Baghdasaryan
2022-09-09 16:12 ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 18/28] mm: add FAULT_FLAG_VMA_LOCK flag Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-09 14:26 ` Laurent Dufour
2022-09-09 14:26 ` Laurent Dufour
2022-09-09 14:26 ` Laurent Dufour
2022-09-01 17:35 ` [RFC PATCH RESEND 19/28] mm: disallow do_swap_page to handle page faults under VMA lock Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-06 19:39 ` Peter Xu
2022-09-06 19:39 ` Peter Xu
2022-09-06 19:39 ` Peter Xu
2022-09-06 20:08 ` Suren Baghdasaryan
2022-09-06 20:08 ` Suren Baghdasaryan
2022-09-06 20:08 ` Suren Baghdasaryan
2022-09-06 20:22 ` Peter Xu
2022-09-06 20:22 ` Peter Xu
2022-09-06 20:22 ` Peter Xu
2022-09-07 0:58 ` Suren Baghdasaryan
2022-09-07 0:58 ` Suren Baghdasaryan
2022-09-07 0:58 ` Suren Baghdasaryan
2022-09-09 14:26 ` Laurent Dufour
2022-09-09 14:26 ` Laurent Dufour
2022-09-09 14:26 ` Laurent Dufour
2022-09-01 17:35 ` [RFC PATCH RESEND 20/28] mm: introduce per-VMA lock statistics Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-09 14:28 ` Laurent Dufour
2022-09-09 14:28 ` Laurent Dufour
2022-09-09 14:28 ` Laurent Dufour
2022-09-09 16:11 ` Suren Baghdasaryan
2022-09-09 16:11 ` Suren Baghdasaryan
2022-09-09 16:11 ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 21/28] mm: introduce find_and_lock_anon_vma to be used from arch-specific code Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-09 14:38 ` Laurent Dufour
2022-09-09 14:38 ` Laurent Dufour
2022-09-09 14:38 ` Laurent Dufour
2022-09-09 16:10 ` Suren Baghdasaryan
2022-09-09 16:10 ` Suren Baghdasaryan
2022-09-09 16:10 ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 22/28] x86/mm: try VMA lock-based page fault handling first Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 23/28] x86/mm: define ARCH_SUPPORTS_PER_VMA_LOCK Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 20:20 ` Kent Overstreet
2022-09-01 20:20 ` Kent Overstreet
2022-09-01 20:20 ` Kent Overstreet
2022-09-01 23:17 ` Suren Baghdasaryan
2022-09-01 23:17 ` Suren Baghdasaryan
2022-09-01 23:17 ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 24/28] arm64/mm: try VMA lock-based page fault handling first Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 25/28] arm64/mm: define ARCH_SUPPORTS_PER_VMA_LOCK Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 26/28] powerc/mm: try VMA lock-based page fault handling first Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 27/28] powerpc/mm: define ARCH_SUPPORTS_PER_VMA_LOCK Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 28/28] kernel/fork: throttle call_rcu() calls in vm_area_free Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan
2022-09-09 15:19 ` Laurent Dufour
2022-09-09 15:19 ` Laurent Dufour
2022-09-09 15:19 ` Laurent Dufour
2022-09-09 16:02 ` Suren Baghdasaryan
2022-09-09 16:02 ` Suren Baghdasaryan
2022-09-09 16:02 ` Suren Baghdasaryan
2022-09-09 16:14 ` Laurent Dufour
2022-09-09 16:14 ` Laurent Dufour
2022-09-09 16:14 ` Laurent Dufour
2022-09-01 20:58 ` [RFC PATCH RESEND 00/28] per-VMA locks proposal Kent Overstreet
2022-09-01 20:58 ` Kent Overstreet
2022-09-01 20:58 ` Kent Overstreet
2022-09-01 23:26 ` Suren Baghdasaryan
2022-09-01 23:26 ` Suren Baghdasaryan
2022-09-01 23:26 ` Suren Baghdasaryan
2022-09-11 9:35 ` Vlastimil Babka
2022-09-11 9:35 ` Vlastimil Babka
2022-09-11 9:35 ` Vlastimil Babka
2022-09-28 2:28 ` Suren Baghdasaryan
2022-09-28 2:28 ` Suren Baghdasaryan
2022-09-28 2:28 ` Suren Baghdasaryan
2022-09-29 11:18 ` Vlastimil Babka [this message]
2022-09-29 11:18 ` Vlastimil Babka
2022-09-29 11:18 ` Vlastimil Babka
2022-09-02 7:42 ` Peter Zijlstra
2022-09-02 7:42 ` Peter Zijlstra
2022-09-02 7:42 ` Peter Zijlstra
2022-09-02 14:45 ` Suren Baghdasaryan
2022-09-02 14:45 ` Suren Baghdasaryan
2022-09-02 14:45 ` Suren Baghdasaryan
2022-09-05 12:32 ` Michal Hocko
2022-09-05 12:32 ` Michal Hocko
2022-09-05 12:32 ` Michal Hocko
2022-09-05 18:32 ` Suren Baghdasaryan
2022-09-05 18:32 ` Suren Baghdasaryan
2022-09-05 18:32 ` Suren Baghdasaryan
2022-09-05 20:35 ` Kent Overstreet
2022-09-05 20:35 ` Kent Overstreet
2022-09-05 20:35 ` Kent Overstreet
2022-09-06 15:46 ` Suren Baghdasaryan
2022-09-06 15:46 ` Suren Baghdasaryan
2022-09-06 15:46 ` Suren Baghdasaryan
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=621612d7-c537-3971-9520-a3dec7b43cb4@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=bigeasy@linutronix.de \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=jglisse@google.com \
--cc=joelaf@google.com \
--cc=kent.overstreet@linux.dev \
--cc=kernel-team@android.com \
--cc=laurent.dufour@fr.ibm.com \
--cc=ldufour@linux.ibm.com \
--cc=liam.howlett@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luto@kernel.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=michel@lespinasse.org \
--cc=minchan@google.com \
--cc=paulmck@kernel.org \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=songliubraving@fb.com \
--cc=surenb@google.com \
--cc=willy@infradead.org \
--cc=x86@kernel.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.