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

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <643703892094_69bfb294a3@willemb.c.googlers.com.notmuch>
Date:   Wed, 12 Apr 2023 15:16:25 -0400
From:   Willem de Bruijn <willemdebruijn.kernel@...il.com>
To:     Sasha Levin <sashal@...nel.org>,
        Pavan Kumar Linga <pavan.kumar.linga@...el.com>
Cc:     intel-wired-lan@...ts.osuosl.org, willemb@...gle.com,
        pabeni@...hat.com, netdev@...r.kernel.org,
        jesse.brandeburg@...el.com, edumazet@...gle.com,
        anthony.l.nguyen@...el.com, kuba@...nel.org, decot@...gle.com,
        davem@...emloft.net
Subject: Re: [Intel-wired-lan] [PATCH net-next v2 00/15] Introduce Intel IDPF
 driver

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.

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.