[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230130123505.GA19948@lst.de>
Date: Mon, 30 Jan 2023 13:35:05 +0100
From: Christoph Hellwig <hch@....de>
To: Max Gurtovoy <mgurtovoy@...dia.com>
Cc: Christoph Hellwig <hch@....de>, Leon Romanovsky <leon@...nel.org>,
Jason Gunthorpe <jgg@...dia.com>,
Bryan Tan <bryantan@...are.com>,
Eric Dumazet <edumazet@...gle.com>,
Israel Rukshin <israelr@...dia.com>,
Jakub Kicinski <kuba@...nel.org>, Jens Axboe <axboe@...com>,
Keith Busch <kbusch@...nel.org>, linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-rdma@...r.kernel.org,
linux-trace-kernel@...r.kernel.org,
Masami Hiramatsu <mhiramat@...nel.org>, netdev@...r.kernel.org,
Paolo Abeni <pabeni@...hat.com>,
Saeed Mahameed <saeedm@...dia.com>,
Sagi Grimberg <sagi@...mberg.me>,
Selvin Xavier <selvin.xavier@...adcom.com>,
Steven Rostedt <rostedt@...dmis.org>,
Vishnu Dasa <vdasa@...are.com>,
Yishai Hadas <yishaih@...dia.com>
Subject: Re: [PATCH rdma-next 00/13] Add RDMA inline crypto support
On Wed, Jan 18, 2023 at 04:20:27PM +0200, Max Gurtovoy wrote:
> Today, if one would like to run both features using a capable device then
> the PI will be offloaded (no SW fallback) and the Encryption will be using
> SW fallback.
It's not just running both - it's offering both as currently registering
these fatures is mutally incompatible.
Powered by blists - more mailing lists