[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190130155758.3a6be144@cakuba.hsd1.ca.comcast.net>
Date: Wed, 30 Jan 2019 15:57:58 -0800
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: Vasundhara Volam <vasundhara-v.volam@...adcom.com>
Cc: davem@...emloft.net, michael.chan@...adcom.com, jiri@...lanox.com,
mkubecek@...e.cz, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v8 0/8] devlink: Add configuration parameters
support for devlink_port
On Mon, 28 Jan 2019 18:00:19 +0530, Vasundhara Volam wrote:
> This patchset adds support for configuration parameters setting through
> devlink_port. Each device registers supported configuration parameters
> table.
>
> The user can retrieve data on these parameters by
> "devlink port param show" command and can set new value to a
> parameter by "devlink port param set" command.
> All configuration modes supported by devlink_dev are supported
> by devlink_port also.
Hm, I think we were kind of going somewhere with the ethtool/nl
attribute encapsulation idea. You seem to have ignored those comments
on v7 and reposted v8 a day after.
I think we should explore the nesting further. The only obstacle is
that ethtool netlink conversion is not yet finished, but that's just
a simple matter of programming. Do you disagree with that direction?
Please comment.
Powered by blists - more mailing lists