netdev - RE: [Intel-wired-lan] [RFC PATCH] net: add net-device TX clock source selection framework

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] [day] [month] [year] [list]

Message-ID: <SJ2PR11MB84520DB2400F612E1A690AF19B27A@SJ2PR11MB8452.namprd11.prod.outlook.com>
Date: Thu, 31 Jul 2025 20:36:02 +0000
From: "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@...el.com>
To: "Vecera, Ivan" <ivecera@...hat.com>, Jiri Pirko <jiri@...nulli.us>
CC: "Nguyen, Anthony L" <anthony.l.nguyen@...el.com>, "Kitszel, Przemyslaw"
	<przemyslaw.kitszel@...el.com>, "andrew+netdev@...n.ch"
	<andrew+netdev@...n.ch>, "davem@...emloft.net" <davem@...emloft.net>,
	"edumazet@...gle.com" <edumazet@...gle.com>, "kuba@...nel.org"
	<kuba@...nel.org>, "pabeni@...hat.com" <pabeni@...hat.com>,
	"horms@...nel.org" <horms@...nel.org>, "sdf@...ichev.me" <sdf@...ichev.me>,
	"almasrymina@...gle.com" <almasrymina@...gle.com>, "asml.silence@...il.com"
	<asml.silence@...il.com>, "leitao@...ian.org" <leitao@...ian.org>,
	"kuniyu@...gle.com" <kuniyu@...gle.com>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "intel-wired-lan@...ts.osuosl.org"
	<intel-wired-lan@...ts.osuosl.org>, "netdev@...r.kernel.org"
	<netdev@...r.kernel.org>
Subject: RE: [Intel-wired-lan] [RFC PATCH] net: add net-device TX clock source
 selection framework

>From: Ivan Vecera <ivecera@...hat.com>
>Sent: Wednesday, July 30, 2025 4:45 PM
>
>On 30. 07. 25 2:26 odp., Jiri Pirko wrote:
>> Tue, Jul 29, 2025 at 12:45:28PM +0200, arkadiusz.kubalewski@...el.com
>wrote:
>>
>> [...]
>>
>>> User interface:
>>> - Read /sys/class/net/<device>/tx_clk/<clock_name> to get status
>>> (0/1)
>>> - Write "1" to switch to that clock source
>>
>> I wonder, if someone invented a time machine and sent me back to 2005...
>>
>> [...]
>>
>+1
>why do we have netlink based interfaces for configuration...?
>
>Wouldn't be better to implement such thing to be configurable via ip link
>or ethtool??
>
>E.g.
>ip link set eth0 tx-clk <clock_name>
>
>--or--
>ethtool --set-tx-clk/--show-tx-clk eth0 <clock_name>
>
>Ivan
>

Hmm, sounds for me, looks clean and easy to understand.

Thank you!
Arkadiusz