[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJieiUiwx+1J9eUvw7woviALNDyFDEJGPfgGjjbph+xBP6xV_g@mail.gmail.com>
Date: Thu, 12 Oct 2017 07:51:57 -0700
From: Roopa Prabhu <roopa@...ulusnetworks.com>
To: Steve Lin <steven.lin1@...adcom.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Jiri Pirko <jiri@...lanox.com>,
"davem@...emloft.net" <davem@...emloft.net>,
Michael Chan <michael.chan@...adcom.com>,
linux-pci@...r.kernel.org,
"John W. Linville" <linville@...driver.com>,
Andy Gospodarek <gospo@...adcom.com>
Subject: Re: [RFC 0/3] Adding config get/set to devlink
On Thu, Oct 12, 2017 at 7:45 AM, Steve Lin <steven.lin1@...adcom.com> wrote:
> Hi Roopa,
>
> The attributes added in this patchset are not really the same type as
> ethtool - these are more device configuration type attributes. The
> speeds you saw, for example, affect the pre-OS [i.e. PXE boot time]
> configuration for a port, and aren't run-time speed changes on a given
> netdev like ethtool configures. As Jiri mentioned, I will add some
> comments to better describe each of the attributes.
>
> So I don't think there's much duplication here with ethtool.
>
> That said, there also shouldn't be anything in the patchset that would
> preclude some future migration of ethtool settings to using devlink or
> rtnetlink API.
>
ok, ack, thanks for the clarification. Just trying to find a best
netlink place for future ethtool migration to netlink.
Powered by blists - more mailing lists