[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMjkvvwfg_9hkGz0B5+51S85ZFTg-aZtBFCfLA1m3b=EmA@mail.gmail.com>
Date: Wed, 20 Dec 2017 12:31:05 +0200
From: Or Gerlitz <gerlitz.or@...il.com>
To: Boris Pismenny <borisp@...lanox.com>
Cc: Jiri Pirko <jiri@...nulli.us>, Ilya Lesokhin <ilyal@...lanox.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"davejwatson@...com" <davejwatson@...com>,
"tom@...bertland.com" <tom@...bertland.com>,
"hannes@...essinduktion.org" <hannes@...essinduktion.org>,
Aviad Yehezkel <aviadye@...lanox.com>,
Liran Liss <liranl@...lanox.com>
Subject: Re: [PATCH v3 net-next 0/6] tls: Add generic NIC offload infrastructure
> It is fundamental requirement to show a use-case along with infra-structure.
To make it clear, sometimes you don't have yet the full HW/FW/FPGA solution
when you come to upstream the infra code. In that case you do the driver code
and submit it based on HW emulator run, this is common the netdev community
and done by few vendors among them us.
Or.
Powered by blists - more mailing lists