From: Greg KH <gregkh@linuxfoundation.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: stable@vger.kernel.org, Wang Kefeng <wangkefeng.wang@huawei.com>,
Russell King <rmk+kernel@armlinux.org.uk>
Subject: Re: [PATCH 1/2] ARM: 9328/1: mm: try VMA lock-based page fault handling first
Date: Tue, 20 Feb 2024 21:20:14 +0100 [thread overview]
Message-ID: <2024022058-huskiness-previous-c334@gregkh> (raw)
In-Reply-To: <20240220190351.39815-1-surenb@google.com>
On Tue, Feb 20, 2024 at 11:03:50AM -0800, Suren Baghdasaryan wrote:
> From: Wang Kefeng <wangkefeng.wang@huawei.com>
>
> Attempt VMA lock-based page fault handling first, and fall back to the
> existing mmap_lock-based handling if that fails, the ebizzy benchmark
> shows 25% improvement on qemu with 2 cpus.
>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
> ---
> arch/arm/Kconfig | 1 +
> arch/arm/mm/fault.c | 30 ++++++++++++++++++++++++++++++
> 2 files changed, 31 insertions(+)
No git id?
What kernel branch(s) does this go to?
confused,
greg k-h
next prev parent reply other threads:[~2024-02-20 20:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 18:44 FAILED: patch "[PATCH] arch/arm/mm: fix major fault accounting when retrying under" failed to apply to 6.7-stable tree gregkh
2024-02-20 19:02 ` [PATCH 6.7.y] arch/arm/mm: fix major fault accounting when retrying under per-VMA lock Suren Baghdasaryan
2024-02-20 19:07 ` Suren Baghdasaryan
2024-02-20 19:03 ` [PATCH 1/2] ARM: 9328/1: mm: try VMA lock-based page fault handling first Suren Baghdasaryan
2024-02-20 19:03 ` [PATCH 2/2] arch/arm/mm: fix major fault accounting when retrying under per-VMA lock Suren Baghdasaryan
2024-02-20 20:20 ` Greg KH
2024-02-20 20:20 ` Greg KH [this message]
2024-02-20 20:23 ` [PATCH 1/2] ARM: 9328/1: mm: try VMA lock-based page fault handling first Suren Baghdasaryan
2024-02-20 20:46 ` Greg KH
2024-02-20 20:54 ` 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=2024022058-huskiness-previous-c334@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=wangkefeng.wang@huawei.com \
/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