netdev - Re: [PATCH v11 net-next 0/8] PHC support in ENA 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: <20250527074419.40163789@kernel.org>
Date: Tue, 27 May 2025 07:44:19 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: David Arinzon <darinzon@...zon.com>, David Miller <davem@...emloft.net>,
 netdev@...r.kernel.org, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
 <pabeni@...hat.com>, Simon Horman <horms@...nel.org>, Richard Cochran
 <richardcochran@...il.com>, "Woodhouse, David" <dwmw@...zon.com>,
 "Machulsky, Zorik" <zorik@...zon.com>, "Matushevsky, Alexander"
 <matua@...zon.com>, Saeed Bshara <saeedb@...zon.com>, "Wilson, Matt"
 <msw@...zon.com>, "Liguori, Anthony" <aliguori@...zon.com>, "Bshara, Nafea"
 <nafea@...zon.com>, "Schmeilin, Evgeny" <evgenys@...zon.com>, "Belgazal,
 Netanel" <netanel@...zon.com>, "Saidi, Ali" <alisaidi@...zon.com>,
 "Herrenschmidt, Benjamin" <benh@...zon.com>, "Kiyanovski, Arthur"
 <akiyano@...zon.com>, "Dagan, Noam" <ndagan@...zon.com>, "Bernstein, Amit"
 <amitbern@...zon.com>, "Agroskin, Shay" <shayagr@...zon.com>, "Ostrovsky,
 Evgeny" <evostrov@...zon.com>, "Tabachnik, Ofir" <ofirt@...zon.com>,
 "Machnikowski, Maciek" <maciek@...hnikowski.net>, Rahul Rameshbabu
 <rrameshbabu@...dia.com>, Gal Pressman <gal@...dia.com>, Vadim Fedorenko
 <vadim.fedorenko@...ux.dev>, Andrew Lunn <andrew@...n.ch>, Leon Romanovsky
 <leon@...nel.org>
Subject: Re: [PATCH v11 net-next 0/8] PHC support in ENA driver

On Mon, 26 May 2025 11:53:14 +0200 Jiri Pirko wrote:
> Could you please add very simple devlink_port instance of flavour
> PHYSICAL and link it with netdev? Having devlink instance without the
> port related to the netdev looks a bit odd.

'Physical' seems inappropriate for a "host side of an IPU".
PCI PF if anything, but also I disagree that we need every devlink
instance to have a port. PTP clocks use devlink and are not networking
devices at all.