From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C018FEB64DB for ; Tue, 20 Jun 2023 19:40:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230449AbjFTTk1 (ORCPT ); Tue, 20 Jun 2023 15:40:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33702 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229718AbjFTTkZ (ORCPT ); Tue, 20 Jun 2023 15:40:25 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8E59E170A for ; Tue, 20 Jun 2023 12:40:24 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 099CD6118E for ; Tue, 20 Jun 2023 19:40:24 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id 6150CC433C0; Tue, 20 Jun 2023 19:40:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1687290023; bh=zgcTRaso7zOqdnf27+oRPafh2nunNGgBt0ylwF5bYSw=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=sSgig7NeqP/GSgCDTgstKw7jdR1p7DQ1e20gTHemkiS4JTYy+Vpyi+MR39WurVSeX 4hDIImqOsYlwr0mCn92So/kIeb2BGGe8uw21kh8pYKEuiZ+vWLRdVfuwHcKXN8/n98 4id4047RpyUW/CkOQf1vMRaKEMGA4LWjcgNFK+/463G1zs1lEmkyYPVhoDLm084VQs e/E+3cgtMwlVA1EhAzIeVVnUJ9dYzDr1zoU7E43MTeHHc5Tt5MB1ink2O7uxnyyL3T LisiPI94iXwF87wC1Nqn5tEaP16s9reUJNrBORuQV3lHkHRkXBYZKYeLCM6au2xq/6 MC7aJJLdVxLxw== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id 44271E301FA; Tue, 20 Jun 2023 19:40:23 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PATCH] riscv: mm: try VMA lock-based page fault handling first From: patchwork-bot+linux-riscv@kernel.org Message-Id: <168729002327.20607.14070522749867476225.git-patchwork-notify@kernel.org> Date: Tue, 20 Jun 2023 19:40:23 +0000 References: <20230523165942.2630-1-jszhang@kernel.org> In-Reply-To: <20230523165942.2630-1-jszhang@kernel.org> To: Jisheng Zhang Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com, palmer@dabbelt.com, aou@eecs.berkeley.edu, linux-kernel@vger.kernel.org, surenb@google.com Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello: This patch was applied to riscv/linux.git (for-next) by Palmer Dabbelt : On Wed, 24 May 2023 00:59:42 +0800 you 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. > > [...] Here is the summary with links: - riscv: mm: try VMA lock-based page fault handling first https://git.kernel.org/riscv/c/648321fa0d97 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html