All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Antoine Tenart <atenart@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Russell King - ARM Linux admin <linux@armlinux.org.uk>,
	Tobias Waldekranz <tobias@waldekranz.com>,
	Oleksij Rempel <o.rempel@pengutronix.de>,
	Jakub Kicinski <kuba@kernel.org>
Subject: Re: Multi-PHYs and multiple-ports bonding support
Date: Mon, 17 Oct 2022 11:45:43 +0200	[thread overview]
Message-ID: <Y00kRzNegS7Obptd@nanopsycho> (raw)
In-Reply-To: <20221017105100.0cb33490@pc-8.home>

Mon, Oct 17, 2022 at 10:51:00AM CEST, maxime.chevallier@bootlin.com wrote:

[...]


>3) UAPI
>
>From userspace, we would need ways to list the ports, their state, and
>possibly to configure the bonding parameters. for now in ethtool, we
>don't have the notion of port at all, we just have 1 netdevice == 1
>port. Should we therefore create one netdevice per port ? or stick to
>that one interface and refer to its ports with some ethtool parameters ?

I don't like the idea of having 1 netdev per port. Netdev represents
mostly the MAC entity, and there is only one.

[...]


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Jiri Pirko <jiri@resnulli.us>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Antoine Tenart <atenart@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Russell King - ARM Linux admin <linux@armlinux.org.uk>,
	Tobias Waldekranz <tobias@waldekranz.com>,
	Oleksij Rempel <o.rempel@pengutronix.de>,
	Jakub Kicinski <kuba@kernel.org>
Subject: Re: Multi-PHYs and multiple-ports bonding support
Date: Mon, 17 Oct 2022 11:45:43 +0200	[thread overview]
Message-ID: <Y00kRzNegS7Obptd@nanopsycho> (raw)
In-Reply-To: <20221017105100.0cb33490@pc-8.home>

Mon, Oct 17, 2022 at 10:51:00AM CEST, maxime.chevallier@bootlin.com wrote:

[...]


>3) UAPI
>
>From userspace, we would need ways to list the ports, their state, and
>possibly to configure the bonding parameters. for now in ethtool, we
>don't have the notion of port at all, we just have 1 netdevice == 1
>port. Should we therefore create one netdevice per port ? or stick to
>that one interface and refer to its ports with some ethtool parameters ?

I don't like the idea of having 1 netdev per port. Netdev represents
mostly the MAC entity, and there is only one.

[...]


  parent reply	other threads:[~2022-10-17  9:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17  8:51 Multi-PHYs and multiple-ports bonding support Maxime Chevallier
2022-10-17  8:51 ` Maxime Chevallier
2022-10-17  9:24 ` Russell King (Oracle)
2022-10-17  9:24   ` Russell King (Oracle)
2022-10-17 13:03   ` Andrew Lunn
2022-10-17 13:03     ` Andrew Lunn
2022-10-18 11:45     ` Maxime Chevallier
2022-10-18 11:45       ` Maxime Chevallier
2022-10-18  8:02   ` Maxime Chevallier
2022-10-18  8:02     ` Maxime Chevallier
2022-10-18  8:13     ` Russell King (Oracle)
2022-10-18  8:13       ` Russell King (Oracle)
2022-10-18  9:20       ` Maxime Chevallier
2022-10-18  9:20         ` Maxime Chevallier
2022-10-17  9:45 ` Jiri Pirko [this message]
2022-10-17  9:45   ` Jiri Pirko
2022-10-17 10:03 ` Oleksij Rempel
2022-10-17 10:03   ` Oleksij Rempel

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=Y00kRzNegS7Obptd@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=andrew@lunn.ch \
    --cc=atenart@kernel.org \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=tobias@waldekranz.com \
    --cc=vivien.didelot@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.