> -----Original Message-----
> From: Stephen Hemminger <step...@networkplumber.org>
> Sent: Friday, July 17, 2020 1:15 PM
> To: David Miller <da...@davemloft.net>
> Cc: Haiyang Zhang <haiya...@microsoft.com>; Chi Song
> <song....@microsoft.com>; KY Srinivasan <k...@microsoft.com>; Stephen
> Hemminger <sthem...@microsoft.com>; wei....@kernel.org;
> k...@kernel.org; a...@kernel.org; dan...@iogearbox.net; ka...@fb.com;
> songliubrav...@fb.com; y...@fb.com; andr...@fb.com;
> john.fastab...@gmail.com; kpsi...@chromium.org; linux-
> hyp...@vger.kernel.org; netdev@vger.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 <da...@davemloft.net>
> wrote:
>
> > From: Haiyang Zhang <haiya...@microsoft.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.
I think it should be a good long term plan, if going forward more NIC
drivers start to use TX table in the future.
Thanks,
- Haiyang
