From: Eric Biggers <ebiggers@kernel.org>
To: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
linux-nvme@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvmet-tcp: switch to using the crc32c library
Date: Tue, 8 Apr 2025 21:04:15 -0700 [thread overview]
Message-ID: <20250409040415.GB4424@sol.localdomain> (raw)
In-Reply-To: <20250226062841.60688-1-ebiggers@kernel.org>
Hi,
On Tue, Feb 25, 2025 at 10:28:40PM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Now that the crc32c() library function directly takes advantage of
> architecture-specific optimizations, it is unnecessary to go through the
> crypto API. Just use crc32c(). This is much simpler, and it improves
> performance due to eliminating the crypto API overhead.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> drivers/nvme/target/tcp.c | 92 +++++++++++----------------------------
> 1 file changed, 26 insertions(+), 66 deletions(-)
This patch never got applied.
- Eric
next prev parent reply other threads:[~2025-04-09 4:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 6:28 [PATCH] nvmet-tcp: switch to using the crc32c library Eric Biggers
2025-02-26 9:37 ` Hannes Reinecke
2025-02-26 19:01 ` Eric Biggers
2025-02-27 7:26 ` Hannes Reinecke
2025-02-27 8:40 ` Sagi Grimberg
2025-03-02 11:49 ` David Laight
2025-02-27 10:10 ` Sagi Grimberg
2025-04-09 4:04 ` Eric Biggers [this message]
2025-04-09 8:45 ` Christoph Hellwig
2025-04-13 22:10 ` Sagi Grimberg
2025-04-22 7:55 ` Christoph Hellwig
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=20250409040415.GB4424@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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