netdev - Re: [Intel-wired-lan] [PATCH net-next v2 00/15] Introduce Intel IDPF driver

Open Source and information security mailing list archives

Message-ID: <d2585839-fcec-4a68-cc7a-d147ce7deb04@intel.com>
Date:   Wed, 12 Apr 2023 19:03:22 -0500
From:   "Samudrala, Sridhar" <sridhar.samudrala@...el.com>
To:     Willem de Bruijn <willemdebruijn.kernel@...il.com>,
        Sasha Levin <sashal@...nel.org>,
        Pavan Kumar Linga <pavan.kumar.linga@...el.com>
CC:     <willemb@...gle.com>, <decot@...gle.com>, <netdev@...r.kernel.org>,
        <jesse.brandeburg@...el.com>, <edumazet@...gle.com>,
        <intel-wired-lan@...ts.osuosl.org>, <kuba@...nel.org>,
        <anthony.l.nguyen@...el.com>, <pabeni@...hat.com>,
        <davem@...emloft.net>
Subject: Re: [Intel-wired-lan] [PATCH net-next v2 00/15] Introduce Intel IDPF
 driver

On 4/12/2023 2:16 PM, Willem de Bruijn wrote:
> Sasha Levin wrote:
>> On Mon, Apr 10, 2023 at 06:13:39PM -0700, Pavan Kumar Linga wrote:
>>> v1 --> v2: link [1]
>>> * removed the OASIS reference in the commit message to make it clear
>>>    that this is an Intel vendor specific driver
>>
>> How will this work when the OASIS driver is ready down the road?
>>
>> We'll end up with two "idpf" drivers, where one will work with hardware
>> that is not fully spec compliant using this Intel driver, and everything
>> else will use the OASIS driver?
>>
>> Does Intel plan to remove this driver when the OASIS one lands?
>>
>> At the very least, having two "idpf" drivers will be very confusing.
> 
> One approach is that when the OASIS v1 spec is published, this driver
> is updated to match that and moved out of the intel directory.

Yes. We don't want to have 2 idpf drivers in the upstream kernel.
It will be an Intel vendor driver until it becomes a standard.
Hope it will be OK to move the driver out of the intel directory when 
that happens.

> 
> This IPU/DPU/SmartNIC/.. device highly programmable. I assume a goal
> is to make sure that the device meets the new v1 spec. That quite
> likely requires a firmware update, but that is fine.
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan@...osl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

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