netdev - Re: [PATCH net-next v5] eea: Add basic driver framework for Alibaba Elastic Ethernet Adaptor

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: <jhvl3gx63kt3xcgx3o4ppsqftgzupjojf3ygblnrapcneuks5w@cgfydxsalyii>
Date: Tue, 14 Oct 2025 14:19:29 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Xuan Zhuo <xuanzhuo@...ux.alibaba.com>
Cc: netdev@...r.kernel.org, Andrew Lunn <andrew+netdev@...n.ch>, 
	"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, 
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, 
	Wen Gu <guwen@...ux.alibaba.com>, Philo Lu <lulie@...ux.alibaba.com>, 
	Lorenzo Bianconi <lorenzo@...nel.org>, Vadim Fedorenko <vadim.fedorenko@...ux.dev>, 
	Lukas Bulwahn <lukas.bulwahn@...hat.com>, Geert Uytterhoeven <geert+renesas@...der.be>, 
	Vivian Wang <wangruikang@...as.ac.cn>, Troy Mitchell <troy.mitchell@...ux.spacemit.com>, 
	Dust Li <dust.li@...ux.alibaba.com>, alok.a.tiwari@...cle.com, kalesh-anakkur.purayil@...adcom.com
Subject: Re: [PATCH net-next v5] eea: Add basic driver framework for Alibaba
 Elastic Ethernet Adaptor

Mon, Oct 13, 2025 at 04:18:33AM +0200, xuanzhuo@...ux.alibaba.com wrote:
>Add a driver framework for EEA that will be available in the future.
>
>This driver is currently quite minimal, implementing only fundamental
>core functionalities. Key features include: I/O queue management via
>adminq, basic PCI-layer operations, and essential RX/TX data
>communication capabilities. It also supports the creation,
>initialization, and management of network devices (netdev). Furthermore,
>the ring structures for both I/O queues and adminq have been abstracted
>into a simple, unified, and reusable library implementation,
>facilitating future extension and maintenance.

Is this another fbnic-like internally used hw which no-one outside
Alibaba will ever get hands on, do I understand that correctly?