[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230117093619.147acc3f@kernel.org>
Date: Tue, 17 Jan 2023 09:36:19 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Shay Agroskin <shayagr@...zon.com>
Cc: Gal Pressman <gal@...dia.com>,
"Arinzon, David" <darinzon@...zon.com>,
David Miller <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Machulsky, Zorik" <zorik@...zon.com>,
"Matushevsky, Alexander" <matua@...zon.com>,
"Bshara, Saeed" <saeedb@...zon.com>,
"Bshara, Nafea" <nafea@...zon.com>,
"Saidi, Ali" <alisaidi@...zon.com>,
"Kiyanovski, Arthur" <akiyano@...zon.com>,
"Dagan, Noam" <ndagan@...zon.com>,
"Itzko, Shahar" <itzko@...zon.com>,
"Abboud, Osama" <osamaabb@...zon.com>,
"Bernstein, Amit" <amitbern@...zon.com>
Subject: Re: [PATCH V1 net-next 0/5] Add devlink support to ena
On Mon, 16 Jan 2023 16:23:56 +0200 Shay Agroskin wrote:
> Going forward, can I ask what's the community's stand on adding
> sysfs or procfse entries to the driver as means to tweak custom
> device attributes ?
We prefer to avoid both of those.
If you're worried about user having hard time changing the parameter
because the user space ethtool command is out of date - our solution
to that will likely be the "Netlink protocol descriptions in YAML".
With that thing you don't really need a custom CLI tool to issue
Netlink commands. Until it gets merged you may need to hand-craft
the right netlink message in python or another scripting language
of choice :(
Powered by blists - more mailing lists