From: patchwork-bot+linux-riscv@kernel.org
To: Xiao Wang <xiao.w.wang@intel.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, jerry.shih@sifive.com,
nick.knight@sifive.com, ajones@ventanamicro.com,
bjorn@rivosinc.com, andy.chiu@sifive.com,
viro@zeniv.linux.org.uk, cleger@rivosinc.com,
alexghiti@rivosinc.com, haicheng.li@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: uaccess: Relax the threshold for fast path
Date: Wed, 22 May 2024 23:51:47 +0000 [thread overview]
Message-ID: <171642190775.9409.16917538511707082083.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240313091929.4029960-1-xiao.w.wang@intel.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 13 Mar 2024 17:19:29 +0800 you wrote:
> The bytes copy for unaligned head would cover at most SZREG-1 bytes, so
> it's better to set the threshold as >= (SZREG-1 + word_copy stride size)
> which equals to 9*SZREG-1.
>
> Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
> ---
> arch/riscv/lib/uaccess.S | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- riscv: uaccess: Relax the threshold for fast path
https://git.kernel.org/riscv/c/e8c7995ea148
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-05-22 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 9:19 [PATCH] riscv: uaccess: Relax the threshold for fast path Xiao Wang
2024-05-03 12:14 ` Alexandre Ghiti
2024-05-22 23:51 ` patchwork-bot+linux-riscv [this message]
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=171642190775.9409.16917538511707082083.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=haicheng.li@intel.com \
--cc=jerry.shih@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nick.knight@sifive.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xiao.w.wang@intel.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