From: freak07 <michalechner92@googlemail.com>
To: surenb@google.com
Cc: akpm@linux-foundation.org, arjunroy@google.com,
axelrasmussen@google.com, bigeasy@linutronix.de,
chriscli@google.com, dave@stgolabs.net, david@redhat.com,
dhowells@redhat.com, edumazet@google.com, gthelen@google.com,
gurua@google.com, hannes@cmpxchg.org, hughd@google.com,
jannh@google.com, jglisse@google.com, joelaf@google.com,
kent.overstreet@linux.dev, kernel-team@android.com,
ldufour@linux.ibm.com, leewalsh@google.com,
liam.howlett@oracle.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linuxppc-dev@lists.ozlabs.org, lstoakes@gmail.com,
luto@kernel.org, mgorman@techsingularity.net, mhocko@suse.com,
michel@lespinasse.org, minchan@google.com, mingo@redhat.com,
paulmck@kernel.org, peterjung1337@gmail.com, peterx@redhat.com,
peterz@infradead.org, posk@google.com,
punit.agrawal@bytedance.com, rientjes@google.com,
rppt@kernel.org, shakeelb@google.com, soheil@google.com,
songliubraving@fb.com, tatashin@google.com, vbabka@suse.cz,
will@kernel.org, willy@infradead.org, x86@kernel.org
Subject: Re: [PATCH v3 00/35] Per-VMA locks
Date: Fri, 24 Feb 2023 10:21:34 +0100 [thread overview]
Message-ID: <20230224092134.30603-1-michalechner92@googlemail.com> (raw)
In-Reply-To: <20230216051750.3125598-1-surenb@google.com>
Here are some measurements from a Pixel 7 Pro that´s running a kernel either with the Per-VMA locks patchset or without.
If there´s interest I can provide results of other specific apps as well.
Results are from consecutive cold app launches issued with "am start" command spawning the main activity of Slack Android app.
https://docs.google.com/spreadsheets/d/1ktujfcyDmIJoQMWsoizGIE-0A_jMS9VMw_seehUY9s0/edit?usp=sharing
There´s quite a noticeable improvement, as can be seen in the graph. The results were reproducible.
If you have any questions feel free to ask.
_______________________________________________
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:[~2023-02-24 9:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230216051750.3125598-1-surenb@google.com>
[not found] ` <20230216051750.3125598-22-surenb@google.com>
2023-02-16 15:34 ` [PATCH v3 21/35] mm/mmap: write-lock adjacent VMAs if they can grow into unmapped area Liam R. Howlett
[not found] ` <CAJuCfpEkujbHNxNWcWr8bmrsMhXGcpDyraOfQaPAcOH=RQPv5A@mail.gmail.com>
2023-02-17 14:50 ` Liam R. Howlett
[not found] ` <20230216051750.3125598-27-surenb@google.com>
2023-02-16 15:44 ` [PATCH v3 26/35] mm: fall back to mmap_lock if vma->anon_vma is not yet set Matthew Wilcox
2023-02-16 19:43 ` Suren Baghdasaryan
2023-02-17 2:14 ` Suren Baghdasaryan
2023-02-17 16:05 ` Matthew Wilcox
2023-02-17 16:10 ` Suren Baghdasaryan
2023-04-03 19:49 ` Matthew Wilcox
[not found] ` <20230216051750.3125598-24-surenb@google.com>
2023-02-23 20:06 ` [PATCH v3 23/35] mm/mmap: prevent pagefault handler from racing with mmu_notifier registration Liam R. Howlett
[not found] ` <20230216051750.3125598-25-surenb@google.com>
2023-02-23 20:08 ` [PATCH v3 24/35] mm: introduce vma detached flag Liam R. Howlett
[not found] ` <20230216051750.3125598-18-surenb@google.com>
2023-02-23 20:20 ` [PATCH v3 17/35] mm/mmap: write-lock VMA before shrinking or expanding it Liam R. Howlett
2023-02-23 20:28 ` Liam R. Howlett
[not found] ` <CAJuCfpE3YtSQuXJwOYWKe1z9O4GASS9pA_FTWGkdveHb3bcMXA@mail.gmail.com>
2023-02-24 1:46 ` Liam R. Howlett
[not found] ` <CAJuCfpG4JOv4aeJ6KJDi7R649vuhc0h75230ZRJgUg8spqti8w@mail.gmail.com>
2023-02-24 16:14 ` Liam R. Howlett
2023-02-24 9:21 ` freak07 [this message]
2023-02-27 16:50 ` [PATCH v3 00/35] Per-VMA locks Davidlohr Bueso
2023-02-27 17:22 ` 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=20230224092134.30603-1-michalechner92@googlemail.com \
--to=michalechner92@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=arjunroy@google.com \
--cc=axelrasmussen@google.com \
--cc=bigeasy@linutronix.de \
--cc=chriscli@google.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=gthelen@google.com \
--cc=gurua@google.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=jannh@google.com \
--cc=jglisse@google.com \
--cc=joelaf@google.com \
--cc=kent.overstreet@linux.dev \
--cc=kernel-team@android.com \
--cc=ldufour@linux.ibm.com \
--cc=leewalsh@google.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=lstoakes@gmail.com \
--cc=luto@kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=michel@lespinasse.org \
--cc=minchan@google.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterjung1337@gmail.com \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=posk@google.com \
--cc=punit.agrawal@bytedance.com \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=shakeelb@google.com \
--cc=soheil@google.com \
--cc=songliubraving@fb.com \
--cc=surenb@google.com \
--cc=tatashin@google.com \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox