All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Peng Fan <peng.fan@nxp.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Fugang Duan <fugang.duan@nxp.com>,
	Shawn Guo <shawnguo@kernel.org>,
	stefan.agner@toradex.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, krzk@kernel.org,
	Vivien Didelot <vivien.didelot@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Vladimir Oltean <olteanv@gmail.com>,
	Fabio Estevam <festevam@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 0/4] net: l2switch: Provide support for L2 switch on i.MX28 SoC
Date: Fri, 27 Nov 2020 10:16:15 +0100	[thread overview]
Message-ID: <20201127101615.7349b35f@jawa> (raw)
In-Reply-To: <20201127005502.GQ2075216@lunn.ch>


[-- Attachment #1.1: Type: text/plain, Size: 1431 bytes --]

Hi Andrew,

> > (A side question - DSA uses switchdev, so when one shall use
> > switchdev standalone?)  
> 
> DSA gives you a framework for an Ethernet switch connected to a host
> via Ethernet for the data plane. Generally, that Ethernet link to the
> switch is a MAC to MAC connection. It can be PHY to PHY. But those are
> just details. The important thing is you use an Ethernet driver on the
> host.
> 
> If you look at pure switchdev devices, they generally DMA frames
> directly into the switch. There is either one DMA queue per switch
> port, or there is a way to multiplex frames over one DMA queue,
> generally by additional fields in the buffer descriptor.
> 
> For this device, at the moment, it is hard to say which is the best
> fit. A lot will depend on how the FEC driver works, if you can reuse
> it, while still having the degree of control you need over the DMA
> channel. If you can reuse the FEC driver, then a DSA driver might
> work. If the coupling it too loose, and you have to take control of
> the DMA, then a pure switchdev driver seems more appropriate.
> 
>     Andrew
> 

Thanks for the detailed explanation.


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
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: Lukasz Majewski <lukma@denx.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Vladimir Oltean <olteanv@gmail.com>,
	Fugang Duan <fugang.duan@nxp.com>,
	"David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>,
	stefan.agner@toradex.com, krzk@kernel.org,
	Shawn Guo <shawnguo@kernel.org>
Subject: Re: [RFC 0/4] net: l2switch: Provide support for L2 switch on i.MX28 SoC
Date: Fri, 27 Nov 2020 10:16:15 +0100	[thread overview]
Message-ID: <20201127101615.7349b35f@jawa> (raw)
In-Reply-To: <20201127005502.GQ2075216@lunn.ch>

[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]

Hi Andrew,

> > (A side question - DSA uses switchdev, so when one shall use
> > switchdev standalone?)  
> 
> DSA gives you a framework for an Ethernet switch connected to a host
> via Ethernet for the data plane. Generally, that Ethernet link to the
> switch is a MAC to MAC connection. It can be PHY to PHY. But those are
> just details. The important thing is you use an Ethernet driver on the
> host.
> 
> If you look at pure switchdev devices, they generally DMA frames
> directly into the switch. There is either one DMA queue per switch
> port, or there is a way to multiplex frames over one DMA queue,
> generally by additional fields in the buffer descriptor.
> 
> For this device, at the moment, it is hard to say which is the best
> fit. A lot will depend on how the FEC driver works, if you can reuse
> it, while still having the degree of control you need over the DMA
> channel. If you can reuse the FEC driver, then a DSA driver might
> work. If the coupling it too loose, and you have to take control of
> the DMA, then a pure switchdev driver seems more appropriate.
> 
>     Andrew
> 

Thanks for the detailed explanation.


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-11-27  9:18 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 23:24 [RFC 0/4] net: l2switch: Provide support for L2 switch on i.MX28 SoC Lukasz Majewski
2020-11-25 23:24 ` Lukasz Majewski
2020-11-25 23:24 ` [RFC 1/4] net: fec: Move some defines to ./drivers/net/ethernet/freescale/fec.h header Lukasz Majewski
2020-11-25 23:24   ` Lukasz Majewski
2020-11-25 23:24 ` [RFC 2/4] net: dsa: Provide DSA driver for NXP's More Than IP L2 switch Lukasz Majewski
2020-11-25 23:24   ` Lukasz Majewski
2020-11-25 23:24 ` [RFC 3/4] net: imx: l2switch: Adjust fec_main.c to provide support for " Lukasz Majewski
2020-11-25 23:24   ` Lukasz Majewski
2020-11-25 23:24 ` [RFC 4/4] ARM: dts: imx28: Add description for L2 switch on XEA board Lukasz Majewski
2020-11-25 23:24   ` Lukasz Majewski
2020-11-26  0:00 ` [RFC 0/4] net: l2switch: Provide support for L2 switch on i.MX28 SoC Andrew Lunn
2020-11-26  0:00   ` Andrew Lunn
2020-11-26  1:30   ` Florian Fainelli
2020-11-26  1:30     ` Florian Fainelli
2020-11-26  3:10     ` Andrew Lunn
2020-11-26  3:10       ` Andrew Lunn
2020-11-26 10:10       ` Lukasz Majewski
2020-11-26 10:10         ` Lukasz Majewski
2020-11-26 14:45         ` Andrew Lunn
2020-11-26 14:45           ` Andrew Lunn
2020-11-27  0:03           ` Lukasz Majewski
2020-11-27  0:03             ` Lukasz Majewski
2020-11-26 12:30 ` Vladimir Oltean
2020-11-26 12:30   ` Vladimir Oltean
2020-11-26 23:35   ` Lukasz Majewski
2020-11-26 23:35     ` Lukasz Majewski
2020-11-27  0:55     ` Andrew Lunn
2020-11-27  0:55       ` Andrew Lunn
2020-11-27  9:16       ` Lukasz Majewski [this message]
2020-11-27  9:16         ` Lukasz Majewski
2020-11-27  1:08     ` Andrew Lunn
2020-11-27  1:08       ` Andrew Lunn
2020-11-27  9:25       ` Lukasz Majewski
2020-11-27  9:25         ` Lukasz Majewski
2020-11-27 15:10         ` Andrew Lunn
2020-11-27 15:10           ` Andrew Lunn
2021-06-17 11:08       ` Lukasz Majewski
2021-06-17 11:08         ` Lukasz Majewski
2021-06-17 13:57         ` Andrew Lunn
2021-06-17 13:57           ` Andrew Lunn
2020-11-27 19:29     ` Vladimir Oltean
2020-11-27 19:29       ` Vladimir Oltean
2020-11-28  0:33       ` Lukasz Majewski
2020-11-28  0:33         ` Lukasz Majewski
2020-11-28  4:34         ` Florian Fainelli
2020-11-28  4:34           ` Florian Fainelli
2020-11-29 21:59           ` Lukasz Majewski
2020-11-29 21:59             ` Lukasz Majewski

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=20201127101615.7349b35f@jawa \
    --to=lukma@denx.de \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=festevam@gmail.com \
    --cc=fugang.duan@nxp.com \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=peng.fan@nxp.com \
    --cc=shawnguo@kernel.org \
    --cc=stefan.agner@toradex.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.