[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <904a5edf-3f50-5f6f-6bc6-3d1a1a664aa5@grimberg.me>
Date: Thu, 8 Oct 2020 14:51:50 -0700
From: Sagi Grimberg <sagi@...mberg.me>
To: Boris Pismenny <borisp@...lanox.com>, kuba@...nel.org,
davem@...emloft.net, saeedm@...dia.com, hch@....de, axboe@...com,
kbusch@...nel.org, viro@...iv.linux.org.uk, edumazet@...gle.com
Cc: Yoray Zack <yorayz@...lanox.com>,
Ben Ben-Ishay <benishay@...lanox.com>,
boris.pismenny@...il.com, linux-nvme@...ts.infradead.org,
netdev@...r.kernel.org, Or Gerlitz <ogerlitz@...lanox.com>
Subject: Re: [PATCH net-next RFC v1 03/10] net: Introduce crc offload for tcp
ddp ulp
> This commit itroduces support for CRC offload to direct data placement
introduces
> ULP on the receive side. Both DDP and CRC share a common API to
> initialize the offload for a TCP socket. But otherwise, both can
> be executed independently.
From the API it not clear that the offload engine does crc32c, do you
see this extended to other crc types in the future?
Other than this the patch looks good to me,
Reviewed-by: Sagi Grimberg <sagi@...mberg.me>
Powered by blists - more mailing lists