From: patchwork-bot+linux-riscv@kernel.org
To: Wang@ci.codeaurora.org, Xiao W <xiao.w.wang@intel.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, charlie@rivosinc.com,
andy.chiu@sifive.com, conor.dooley@microchip.com,
greentime.hu@sifive.com, ajones@ventanamicro.com,
heiko@sntech.de, david.laight@aculab.com, haicheng.li@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] riscv: Optimize crc32 with Zbc extension
Date: Fri, 12 Jul 2024 10:20:32 +0000 [thread overview]
Message-ID: <172077963248.4770.592373890802161820.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240621054707.1847548-1-xiao.w.wang@intel.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 21 Jun 2024 13:47:07 +0800 you wrote:
> As suggested by the B-ext spec, the Zbc (carry-less multiplication)
> instructions can be used to accelerate CRC calculations. Currently, the
> crc32 is the most widely used crc function inside kernel, so this patch
> focuses on the optimization of just the crc32 APIs.
>
> Compared with the current table-lookup based optimization, Zbc based
> optimization can also achieve large stride during CRC calculation loop,
> meantime, it avoids the memory access latency of the table-lookup based
> implementation and it reduces memory footprint.
>
> [...]
Here is the summary with links:
- [v5] riscv: Optimize crc32 with Zbc extension
https://git.kernel.org/riscv/c/a43fe27d6503
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-07-12 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 5:47 [PATCH v5] riscv: Optimize crc32 with Zbc extension Xiao Wang
2024-07-12 10:20 ` 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=172077963248.4770.592373890802161820.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=Wang@ci.codeaurora.org \
--cc=ajones@ventanamicro.com \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=david.laight@aculab.com \
--cc=greentime.hu@sifive.com \
--cc=haicheng.li@intel.com \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--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