netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: Hariprasad Kelam <hkelam@marvell.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Sunil Goutham <sgoutham@marvell.com>,
	Geetha sowjanya <gakula@marvell.com>,
	Subbaraya Sundeep <sbhatta@marvell.com>,
	Bharat Bhushan <bbhushan2@marvell.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	Kory Maincent <kory.maincent@bootlin.com>,
	Gal Pressman <gal@nvidia.com>, Jianbo Liu <jianbol@nvidia.com>,
	Edward Cree <ecree.xilinx@gmail.com>,
	Breno Leitao <leitao@debian.org>,
	Russell King <linux@armlinux.org.uk>
Subject: Re: [RFC net-next] net: loopback: Extend netdev features with new loopback modes
Date: Fri, 24 Oct 2025 11:11:09 +0200	[thread overview]
Message-ID: <aPtCrc6EPpn_hcYp@pengutronix.de> (raw)
In-Reply-To: <e9aa0470-2bd2-4825-8333-ad9dbc7f40a0@bootlin.com>

On Fri, Oct 24, 2025 at 10:46:14AM +0200, Maxime Chevallier wrote:
> Hi,
> 
> +Russell +Oleksij
> 
> On 24/10/2025 06:48, Hariprasad Kelam wrote:
> > This patch enhances loopback support by exposing new loopback modes
> > (e.g., MAC, SERDES) to userspace. These new modes are added extension
> > to the existing netdev features.
> > 
> > This allows users to select the loopback at specific layer.
> > 
> > Below are new modes added:
> > 
> > MAC near end loopback
> > 
> > MAC far end loopback
> > 
> > SERDES loopback
> > 
> > Depending on the feedback will submit ethtool changes.
> 
> Good to see you're willing to tackle this work. However as Eric says,
> I don't think the netdev_features is the right place for this :
>  - These 3 loopback modes here may not be enough for some plaforms
>  - This eludes all PHY-side and PCS-side loopback modes that we could
>    also use.
> 
> If we want to expose these loopback modes to userspace, we may actually
> need a dedicated ethtool netlink command for loopback configuration and
> control. This could then hit netdev ethtool ops or phy_device ethtool
> ops depending on the selected loopback point.
> 
> If you don't want to deal with the whole complexity of PHY loopback, you
> can for now only hook into a newly introduced netdev ethtool ops dedicated
> to loopback on the ethnl side, but keep the door open for PHY-side
> loopback later on.

Ack, I agree. I would be better to have information and configuration
for all loopbacks in one place.
Will it be possible to reflect the chain of components and level of
related loopbacks? I guess, at least each driver would be able to know
own loopback levels/order.

Please add me in CC if you decide to jump in to this rabbit hole :D

Best Regards,
Oleksij
-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2025-10-24  9:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24  4:48 [RFC net-next] net: loopback: Extend netdev features with new loopback modes Hariprasad Kelam
2025-10-24  6:48 ` Eric Dumazet
2025-10-24  8:46 ` Maxime Chevallier
2025-10-24  9:11   ` Oleksij Rempel [this message]
2025-10-28 14:17     ` Hariprasad Kelam

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=aPtCrc6EPpn_hcYp@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=andrew+netdev@lunn.ch \
    --cc=bbhushan2@marvell.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=gal@nvidia.com \
    --cc=hkelam@marvell.com \
    --cc=horms@kernel.org \
    --cc=jianbol@nvidia.com \
    --cc=kory.maincent@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sbhatta@marvell.com \
    --cc=sgoutham@marvell.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).