From: Stephen Hemminger <stephen@networkplumber.org>
To: David Miller <davem@davemloft.net>
Cc: haiyangz@microsoft.com, Song.Chi@microsoft.com,
kys@microsoft.com, sthemmin@microsoft.com, wei.liu@kernel.org,
kuba@kernel.org, ast@kernel.org, daniel@iogearbox.net,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com, andriin@fb.com,
john.fastabend@gmail.com, kpsingh@chromium.org,
linux-hyperv@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: hyperv: Add attributes to show RX/TX indirection table
Date: Fri, 17 Jul 2020 10:15:23 -0700 [thread overview]
Message-ID: <20200717101523.6573061b@hermes.lan> (raw)
In-Reply-To: <20200717.095535.195550343235350259.davem@davemloft.net>
On Fri, 17 Jul 2020 09:55:35 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: Haiyang Zhang <haiyangz@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.
Alternatively, the hyperv network driver could integrate/replace the
indirection table with something based on current receive flow steering.
next prev parent reply other threads:[~2020-07-17 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 6:04 [PATCH net-next] net: hyperv: Add attributes to show RX/TX indirection table Chi Song
2020-07-17 10:43 ` Wei Liu
2020-07-17 15:24 ` Stephen Hemminger
2020-07-17 16:18 ` Haiyang Zhang
2020-07-17 16:55 ` David Miller
2020-07-17 16:59 ` Haiyang Zhang
2020-07-17 17:15 ` Stephen Hemminger [this message]
2020-07-17 17:33 ` Haiyang Zhang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200717101523.6573061b@hermes.lan \
--to=stephen@networkplumber.org \
--cc=Song.Chi@microsoft.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=haiyangz@microsoft.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@kernel.org \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).