All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Jakub Kicinski <kuba@kernel.org>, Jiri Pirko <jiri@mellanox.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Robin Murphy <robin.murphy@arm.com>,
	Calvin Johnson <calvin.johnson@nxp.com>,
	stuyoder@gmail.com, nleeder@codeaurora.org,
	Ioana Ciornei <ioana.ciornei@nxp.com>,
	Cristi Sovaiala <cristian.sovaiala@nxp.com>,
	Hanjun Guo <guohanjun@huawei.com>, Will Deacon <will@kernel.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Marc Zyngier <maz@kernel.org>,
	Pankaj Bansal <pankaj.bansal@nxp.com>,
	Jon Nettleton <jon@solid-run.com>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Len Brown <lenb@kernel.org>, Jason Cooper <jason@lakedaemon.net>,
	Andy Wang <Andy.Wang@arm.com>,
	Makarand Pawagi <makarand.pawagi@nxp.com>,
	Varun Sethi <V.Sethi@nxp.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Laurentiu Tudor <laurentiu.tudor@nxp.com>,
	Paul Yang <Paul.Yang@arm.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	"<netdev@vger.kernel.org>" <netdev@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Shameerali Kolothum Thodi  <shameerali.kolothum.thodi@huawei.com>,
	Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [EXT] Re: [PATCH] bus: fsl-mc: Add ACPI support for fsl-mc
Date: Sat, 1 Feb 2020 11:49:19 +0000	[thread overview]
Message-ID: <20200201114919.GQ25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200131074050.38d78ff0@cakuba.hsd1.ca.comcast.net>

On Fri, Jan 31, 2020 at 07:40:50AM -0800, Jakub Kicinski wrote:
> On Fri, 31 Jan 2020 15:15:00 +0000, Russell King - ARM Linux admin
> wrote:
> > I have some prototype implementation for driving the QSFP+ cage, but
> > I haven't yet worked out how to sensible deal with the "is it 4x 10G
> > or 1x 40G" issue you mention above, and how to interface the QSFP+
> > driver sensibly with one or four network drivers.
> 
> I'm pretty sure you know this but just FWIW - vendors who do it in FW
> write the current config down in NVM so it doesn't get affected by
> reboots and use devlink port splitting to change it.

+Jiri

I wasn't aware of devlink port splitting, so thanks for that. However,
it could do with some better documentation - there's nothing on it
afaics in the Documentation subdirectory, and "man devlink-port"
doesn't give much away either:

   devlink port split - split devlink port into more
       DEV/PORT_INDEX - specifies the devlink port to operate on.

       count COUNT
              number of ports to split to.

It's the "into more" that's not clear - presumably more ports, and
presumably each port is a network device, but this isn't explained.

I think what this is trying to say is that, if we have a QSFP+ cage
with 4 serdes lines running at 10G, and they are initially treated as
a single 40G ethernet:

	devlink port split device/1 count 4

will then give us four 10G network devices, and:

	devlink port unsplit device/1

will recombine them back to a single 40G network device.

What if someone decides to do:

	devlink port split device/1 count 2

what do we end up with?  Presumably two network devices running with
two serdes lanes each (if supported by the hardware).  At that point
can they then do:

	devlink port split device/2 count 2

and end up with one network device with two 10G serdes lanes, and two
network devices each with one 10G serdes lane, or can port splitting
only be used on the "master" device/port ?

Unfortunately, I don't think I have any network devices that support
this so I can't experiment to find out how this should work; yes, I
have a Mellanox card, but it supports a single 10G SFP+, and therefore
does not support port splitting.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Jakub Kicinski <kuba@kernel.org>, Jiri Pirko <jiri@mellanox.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Calvin Johnson <calvin.johnson@nxp.com>,
	stuyoder@gmail.com, nleeder@codeaurora.org,
	Ioana Ciornei <ioana.ciornei@nxp.com>,
	Cristi Sovaiala <cristian.sovaiala@nxp.com>,
	Hanjun Guo <guohanjun@huawei.com>, Will Deacon <will@kernel.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Marc Zyngier <maz@kernel.org>,
	Pankaj Bansal <pankaj.bansal@nxp.com>,
	Jon Nettleton <jon@solid-run.com>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Len Brown <lenb@kernel.org>, Jason Cooper <jason@lakedaemon.net>,
	Andy Wang <Andy.Wang@arm.com>,
	Makarand Pawagi <makarand.pawagi@nxp.com>,
	Varun Sethi <V.Sethi@nxp.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Laurentiu Tudor <laurentiu.tudor@nxp.com>,
	Paul Yang <Paul.Yang@arm.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	"<netdev@vger.kernel.org>" <netdev@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Robin Murphy <robin.murphy@arm.com>
Subject: Re: [EXT] Re: [PATCH] bus: fsl-mc: Add ACPI support for fsl-mc
Date: Sat, 1 Feb 2020 11:49:19 +0000	[thread overview]
Message-ID: <20200201114919.GQ25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200131074050.38d78ff0@cakuba.hsd1.ca.comcast.net>

On Fri, Jan 31, 2020 at 07:40:50AM -0800, Jakub Kicinski wrote:
> On Fri, 31 Jan 2020 15:15:00 +0000, Russell King - ARM Linux admin
> wrote:
> > I have some prototype implementation for driving the QSFP+ cage, but
> > I haven't yet worked out how to sensible deal with the "is it 4x 10G
> > or 1x 40G" issue you mention above, and how to interface the QSFP+
> > driver sensibly with one or four network drivers.
> 
> I'm pretty sure you know this but just FWIW - vendors who do it in FW
> write the current config down in NVM so it doesn't get affected by
> reboots and use devlink port splitting to change it.

+Jiri

I wasn't aware of devlink port splitting, so thanks for that. However,
it could do with some better documentation - there's nothing on it
afaics in the Documentation subdirectory, and "man devlink-port"
doesn't give much away either:

   devlink port split - split devlink port into more
       DEV/PORT_INDEX - specifies the devlink port to operate on.

       count COUNT
              number of ports to split to.

It's the "into more" that's not clear - presumably more ports, and
presumably each port is a network device, but this isn't explained.

I think what this is trying to say is that, if we have a QSFP+ cage
with 4 serdes lines running at 10G, and they are initially treated as
a single 40G ethernet:

	devlink port split device/1 count 4

will then give us four 10G network devices, and:

	devlink port unsplit device/1

will recombine them back to a single 40G network device.

What if someone decides to do:

	devlink port split device/1 count 2

what do we end up with?  Presumably two network devices running with
two serdes lanes each (if supported by the hardware).  At that point
can they then do:

	devlink port split device/2 count 2

and end up with one network device with two 10G serdes lanes, and two
network devices each with one 10G serdes lane, or can port splitting
only be used on the "master" device/port ?

Unfortunately, I don't think I have any network devices that support
this so I can't experiment to find out how this should work; yes, I
have a Mellanox card, but it supports a single 10G SFP+, and therefore
does not support port splitting.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

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

  reply	other threads:[~2020-02-01 11:49 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28  8:08 [PATCH] bus: fsl-mc: Add ACPI support for fsl-mc Makarand Pawagi
2020-01-28  8:08 ` Makarand Pawagi
2020-01-28 10:58 ` Marc Zyngier
2020-01-28 10:58   ` Marc Zyngier
2020-01-28 11:09 ` Lorenzo Pieralisi
2020-01-28 11:09   ` Lorenzo Pieralisi
2020-01-31 10:35   ` [EXT] " Makarand Pawagi
2020-01-31 10:35     ` Makarand Pawagi
2020-01-31 11:06     ` Lorenzo Pieralisi
2020-01-31 11:06       ` Lorenzo Pieralisi
2020-01-31 11:06     ` Marc Zyngier
2020-01-31 11:06       ` Marc Zyngier
2020-01-31 12:01       ` Ard Biesheuvel
2020-01-31 12:01         ` Ard Biesheuvel
2020-01-31 12:28         ` Jon Nettleton
2020-01-31 12:28           ` Jon Nettleton
2020-01-31 12:48           ` Robin Murphy
2020-01-31 12:48             ` Robin Murphy
2020-01-31 13:11             ` Jon Nettleton
2020-01-31 13:11               ` Jon Nettleton
2020-01-31 13:29               ` Ard Biesheuvel
2020-01-31 13:29                 ` Ard Biesheuvel
2020-01-31 13:39               ` Robin Murphy
2020-01-31 13:39                 ` Robin Murphy
2020-01-31 14:29                 ` Andrew Lunn
2020-01-31 14:29                   ` Andrew Lunn
2020-01-31 14:47                   ` Will Deacon
2020-01-31 14:47                     ` Will Deacon
2020-01-31 15:09                     ` Andrew Lunn
2020-01-31 15:09                       ` Andrew Lunn
2020-01-31 15:14                       ` Jon Nettleton
2020-01-31 15:14                         ` Jon Nettleton
2020-01-31 15:41                         ` Andrew Lunn
2020-01-31 15:41                           ` Andrew Lunn
2020-01-31 15:39                       ` Russell King - ARM Linux admin
2020-01-31 15:39                         ` Russell King - ARM Linux admin
2020-01-31 15:15                   ` Russell King - ARM Linux admin
2020-01-31 15:15                     ` Russell King - ARM Linux admin
2020-01-31 15:40                     ` Jakub Kicinski
2020-01-31 15:40                       ` Jakub Kicinski
2020-02-01 11:49                       ` Russell King - ARM Linux admin [this message]
2020-02-01 11:49                         ` Russell King - ARM Linux admin
2020-02-01 17:36                         ` Jakub Kicinski
2020-02-01 17:36                           ` Jakub Kicinski
2020-02-14 15:05         ` Pankaj Bansal
2020-02-14 15:05           ` Pankaj Bansal
2020-02-14 15:54           ` Marc Zyngier
2020-02-14 15:54             ` Marc Zyngier
2020-02-14 15:58             ` Pankaj Bansal
2020-02-14 15:58               ` Pankaj Bansal
2020-02-14 16:19               ` Lorenzo Pieralisi
2020-02-14 16:19                 ` Lorenzo Pieralisi
2020-02-14 16:35                 ` Pankaj Bansal
2020-02-14 16:35                   ` Pankaj Bansal
2020-02-14 17:49                   ` Lorenzo Pieralisi
2020-02-14 17:49                     ` Lorenzo Pieralisi
2020-02-17 12:35                     ` Pankaj Bansal
2020-02-17 12:35                       ` Pankaj Bansal
2020-02-17 15:25                       ` Lorenzo Pieralisi
2020-02-17 15:25                         ` Lorenzo Pieralisi
2020-02-17 15:35                         ` Marc Zyngier
2020-02-17 15:35                           ` Marc Zyngier
2020-02-17 16:26                           ` Lorenzo Pieralisi
2020-02-17 16:26                             ` Lorenzo Pieralisi
2020-02-18  8:02                         ` Pankaj Bansal (OSS)
2020-02-18  8:02                           ` Pankaj Bansal (OSS)
2020-02-14 16:29               ` Robin Murphy
2020-02-14 16:29                 ` Robin Murphy

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=20200201114919.GQ25745@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=Andy.Wang@arm.com \
    --cc=Paul.Yang@arm.com \
    --cc=V.Sethi@nxp.com \
    --cc=andrew@lunn.ch \
    --cc=ard.biesheuvel@linaro.org \
    --cc=calvin.johnson@nxp.com \
    --cc=cristian.sovaiala@nxp.com \
    --cc=guohanjun@huawei.com \
    --cc=ioana.ciornei@nxp.com \
    --cc=jason@lakedaemon.net \
    --cc=jiri@mellanox.com \
    --cc=jon@solid-run.com \
    --cc=kuba@kernel.org \
    --cc=laurentiu.tudor@nxp.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=makarand.pawagi@nxp.com \
    --cc=maz@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nleeder@codeaurora.org \
    --cc=pankaj.bansal@nxp.com \
    --cc=rjw@rjwysocki.net \
    --cc=robin.murphy@arm.com \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=stuyoder@gmail.com \
    --cc=sudeep.holla@arm.com \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.org \
    /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.