From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Wei Fang <wei.fang@nxp.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, claudiu.manoil@nxp.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: enetc: add ethtool::get_channels support
Date: Wed, 22 Nov 2023 13:01:20 +0200 [thread overview]
Message-ID: <20231122110120.crs4rh2utjweswsc@skbuf> (raw)
In-Reply-To: <20231122102540.3766699-1-wei.fang@nxp.com>
Hi Wei,
On Wed, Nov 22, 2023 at 06:25:40PM +0800, Wei Fang wrote:
> Since ETHTOOL_MSG_RSS_GET netlink message [1] has been applied to
> ethtool tree, there is a netlink error when using "ethtool -x eno0"
> command to get RSS information from fsl-enetc driver, and the user
> cannot get the information, the error logs are as follows:
>
> root@ls1028ardb:~# ./ethtool -x eno0
> netlink error: Operation not supported
>
> The rationale is that ethtool will issue a ETHTOOL_MSG_CHANNELS_GET
> netlink message to get the number of Rx ring. However, the fsl-enetc
> driver doesn't support ethtool::get_channels, so it directly returns
> -EOPNOTSUPP error.
>
> [1]: https://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/ethtool.git/commit/?id=ffab99c1f3820e21d65686e030dcf2c4fd0a8bd0
>
> Signed-off-by: Wei Fang <wei.fang@nxp.com>
> ---
I think we have 2 problems on our hands.
1. enetc is not the only driver that doesn't report ETHTOOL_MSG_CHANNELS_GET.
So it is a general issue for Sudheer Mogilappagari's implementation
of "ethtool -x" using netlink. The ioctl-based implementation used to
look at ETHTOOL_GRXRINGS which was handled in the kernel through
ethtool_ops :: get_rxnfc.
2. I used to have a different implementation (and interpretation) of
ETHTOOL_MSG_CHANNELS_GET for enetc anyway, which associated channels
not with rings, but with interrupt vectors (making the reported
channels combined):
https://patchwork.kernel.org/project/netdevbpf/patch/20230206100837.451300-6-vladimir.oltean@nxp.com/
I would suggest finding a way for the user space implementation to not
assume that ETHTOOL_MSG_CHANNELS_GET is implemented by the driver.
next prev parent reply other threads:[~2023-11-22 11:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 10:25 [PATCH net-next] net: enetc: add ethtool::get_channels support Wei Fang
2023-11-22 10:49 ` [EXT] " Suman Ghosh
2023-11-23 1:49 ` Wei Fang
2023-11-22 11:01 ` Vladimir Oltean [this message]
2023-11-23 2:09 ` Wei Fang
2023-11-23 9:40 ` Vladimir Oltean
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=20231122110120.crs4rh2utjweswsc@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wei.fang@nxp.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