[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aCbWAFNoBUjci7HG@infradead.org>
Date: Thu, 15 May 2025 23:06:56 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Eric Biggers <ebiggers@...nel.org>
Cc: Christoph Hellwig <hch@...radead.org>, netdev@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-sctp@...r.kernel.org,
linux-rdma@...r.kernel.org, linux-kernel@...r.kernel.org,
Daniel Borkmann <daniel@...earbox.net>,
Marcelo Ricardo Leitner <marcelo.leitner@...il.com>,
Sagi Grimberg <sagi@...mberg.me>, Ard Biesheuvel <ardb@...nel.org>
Subject: Re: [PATCH net-next 09/10] nvme-tcp: use crc32c() and
skb_copy_and_crc32c_datagram_iter()
On Thu, May 15, 2025 at 10:31:00PM -0700, Eric Biggers wrote:
> +static inline __le32 nvme_tcp_hdgst(const void *pdu, size_t len)
> +{
> + return cpu_to_le32(~crc32c(NVME_TCP_CRC_SEED, pdu, len));
> }
This drops the unaligned handling. Now in the NVMe protocol it will
always be properly aligned, but my TCP-foo is not good enough to
remember if the networking code will also guarantee 32-bit alignment
for the start of the packet?
Otherwise this looks great:
Reviewed-by: Christoph Hellwig <hch@....de>
Powered by blists - more mailing lists