[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200717101523.6573061b@hermes.lan>
Date: Fri, 17 Jul 2020 10:15:23 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: David Miller <davem@...emloft.net>
Cc: haiyangz@...rosoft.com, Song.Chi@...rosoft.com, kys@...rosoft.com,
sthemmin@...rosoft.com, wei.liu@...nel.org, kuba@...nel.org,
ast@...nel.org, daniel@...earbox.net, kafai@...com,
songliubraving@...com, yhs@...com, andriin@...com,
john.fastabend@...il.com, kpsingh@...omium.org,
linux-hyperv@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] net: hyperv: Add attributes to show RX/TX
indirection table
On Fri, 17 Jul 2020 09:55:35 -0700 (PDT)
David Miller <davem@...emloft.net> wrote:
> From: Haiyang Zhang <haiyangz@...rosoft.com>
> Date: Fri, 17 Jul 2020 16:18:11 +0000
>
> > Also in some minimal installation, "ethtool" may not always be
> > installed.
>
> This is never an argument against using the most well suited API for
> exporting information to the user.
>
> You can write "minimal" tools that just perform the ethtool netlink
> operations you require for information retrieval, you don't have to
> have the ethtool utility installed.
Would it be better in the long term to make the transmit indirection
table available under the new rt_netlink based API's for ethtool?
I can imagine that other hardware or hypervisors might have the
same kind of transmit mapping.
Alternatively, the hyperv network driver could integrate/replace the
indirection table with something based on current receive flow steering.
Powered by blists - more mailing lists