| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 2 Jun 2021 19:58:36 +0300
From: Shai Malin <malin1024@...il.com>
To: Shai Malin <smalin@...vell.com>
Cc: netdev@...r.kernel.org, linux-nvme@...ts.infradead.org,
davem@...emloft.net, kuba@...nel.org,
Sagi Grimberg <sagi@...mberg.me>, hch@....de, axboe@...com,
kbusch@...nel.org, Ariel Elior <aelior@...vell.com>,
Michal Kalderon <mkalderon@...vell.com>, okulkarni@...vell.com,
pkushwaha@...vell.com, prabhakar.pkin@...il.com
Subject: Re: [RFC PATCH v7 00/27] NVMeTCP Offload ULP and QEDN Device Driver
On 6/1/21 1:53 AM, Shai Malin wrote:
> With the goal of enabling a generic infrastructure that allows NVMe/TCP
> offload devices like NICs to seamlessly plug into the NVMe-oF stack, this
> patch series introduces the nvme-tcp-offload ULP host layer, which will
> be a new transport type called "tcp-offload" and will serve as an
> abstraction layer to work with vendor specific nvme-tcp offload drivers.
If there are no additional comments on RFC v7, I will split the RFC series
between the following non-RFC sub-series:
- Part 1 (RFC patch 1-8): NVMeTCP Offload ULP
The nvme-tcp-offload patches will be sent to
'linux-nvme@...ts.infradead.org'.
- Part 2 (RFC patches 9-15): QED NVMeTCP Offload
The qed infrastructure will be sent to 'netdev@...r.kernel.org'.
Once part 1 and 2 are accepted:
- Part 3 (RFC patches 16-27): QEDN NVMeTCP Offload
The qedn patches will be sent to 'linux-nvme@...ts.infradead.org'.
Powered by blists - more mailing lists