Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
In-Reply-To: <20230523165942.2630-1-jszhang@kernel.org>
References: <20230523165942.2630-1-jszhang@kernel.org>
Subject: Re: [PATCH] riscv: mm: try VMA lock-based page fault handling
 first
Message-Id: <168728927543.19726.6287680101393948485.b4-ty@rivosinc.com>
Date:   Tue, 20 Jun 2023 12:27:55 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Cc:     linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
        Suren Baghdasaryan <surenb@google.com>
From:   Palmer Dabbelt <palmer@rivosinc.com>
To:     Paul Walmsley <paul.walmsley@sifive.com>,
        Palmer Dabbelt <palmer@dabbelt.com>,
        Albert Ou <aou@eecs.berkeley.edu>,
        Jisheng Zhang <jszhang@kernel.org>
Precedence: bulk


On Wed, 24 May 2023 00:59:42 +0800, Jisheng Zhang wrote:
> Attempt VMA lock-based page fault handling first, and fall back to the
> existing mmap_lock-based handling if that fails.
> 
> A simple running the ebizzy benchmark on Lichee Pi 4A shows that
> PER_VMA_LOCK can improve the ebizzy benchmark by about 32.68%. In
> theory, the more CPUs, the bigger improvement, but I don't have any
> HW platform which has more than 4 CPUs.
> 
> [...]

Applied, thanks!

[1/1] riscv: mm: try VMA lock-based page fault handling first
      https://git.kernel.org/palmer/c/648321fa0d97

Best regards,
-- 
Palmer Dabbelt <palmer@rivosinc.com>