netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Andy Gospodarek <gospo@cumulusnetworks.com>,
	"David S. Miller" <davem@davemloft.net>,
	Network Development <netdev@vger.kernel.org>,
	Jonas Gorski <jogo@openwrt.org>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	Felix Fietkau <nbd@openwrt.org>
Subject: Re: [PATCH] net: phy: b53: switchdev driver for Broadcom BCM53xx switches
Date: Wed, 25 Feb 2015 09:07:51 +0100	[thread overview]
Message-ID: <20150225080751.GC2039@nanopsycho.orion> (raw)
In-Reply-To: <CACna6rzMcVd7SJ6NTBrrWtXe1ZTgxF5tgVb08eaPxxwTxWU1cg@mail.gmail.com>

Wed, Feb 25, 2015 at 08:03:48AM CET, zajec5@gmail.com wrote:
>On 25 February 2015 at 01:39, Florian Fainelli <f.fainelli@gmail.com> wrote:
>> On 24/02/15 16:15, Andrew Lunn wrote:
>>> On Tue, Feb 24, 2015 at 02:55:58PM -0800, Florian Fainelli wrote:
>>>> On 24/02/15 14:50, Rafa?? Mi??ecki wrote:
>>>>> As said in the commit message, these switches are really simple
>>>>> devices. We can't actually send packets to the particular ports
>>>>> (unless something has changed in the more recent hardware).
>>>>
>>>> These switches all support Broadcom tags, so you could use your host CPU
>>>> Ethernet MAC to send/receive packets to/from specific ports of the
>>>> switch, and then this is just like DSA, but everything that you say
>>>> below is true.
>>>
>>> If this hardware does support the concept of tags compatible to the
>>> existing Broadcom Starfighter 2, should we not do that? Is there a
>>> good reason these chips should use a difference abstraction than
>>> Starfighter 2 and the Marvell devices?
>>
>> No, I think that would be a reasonable thing to do, I am still a little
>> unclear how the older BCM5325 and friends work with respect to broadcom
>> tags, but regardless, DSA now understands switches that do not support
>> tags, so we should be good with some sort of b53 library.
>
>DSA doesn't allow me to use switch (hardware) VLANs. I would need to
>handle all forwarding in CPU. The most powerful Broadcom MIPS SoC -
>BCM4706 - can handle about 130 Mb/s. Less powerful - BCM4718A1 - only
>about 50 Mb/s.
>This is way too bad for performance when there is a 1 Gb/s switch and
>too bad for CPU usage.

Please correct me if I'm wrong Florian, but I believe that DSA does
allow setting up chips to do forwarding without packets going to CPU.

b53 looks like it fits nicely into DSA architecture. I believe that it
should be integrated there.

>
>I guess the whole idea of switchdev was to allow what proposed version
>of b53 does? To handle VLANs in hardware.
>
>-- 
>Rafał

  reply	other threads:[~2015-02-25  8:07 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 17:42 [PATCH] net: phy: b53: switchdev driver for Broadcom BCM53xx switches Rafał Miłecki
2015-02-24 17:47 ` Rafał Miłecki
2015-02-24 21:51 ` Andrew Lunn
2015-02-24 22:29   ` Rafał Miłecki
2015-02-25  0:51     ` Andrew Lunn
2015-02-24 22:30 ` Andy Gospodarek
2015-02-24 22:50   ` Rafał Miłecki
2015-02-24 22:55     ` Florian Fainelli
2015-02-25  0:15       ` Andrew Lunn
2015-02-25  0:39         ` Florian Fainelli
2015-02-25  7:03           ` Rafał Miłecki
2015-02-25  8:07             ` Jiri Pirko [this message]
2015-02-25 14:03             ` Andrew Lunn
2015-02-25 14:17               ` Rafał Miłecki
2015-02-25 14:19                 ` Andrew Lunn
2015-02-26 14:58                   ` Rafał Miłecki
2015-02-26 15:18                     ` Andrew Lunn
2015-02-26 15:30                       ` Rafał Miłecki
2015-02-26 15:36                         ` Andrew Lunn
2015-02-26 15:49                           ` Rafał Miłecki
2015-02-26 16:21                             ` Andrew Lunn
2015-02-26 17:58                             ` Florian Fainelli
2015-02-26 18:26                               ` Scott Feldman
2015-02-26 17:57                           ` Florian Fainelli
2015-02-25 15:46               ` Andy Gospodarek
2015-02-25 17:23                 ` Rafał Miłecki
2015-02-25 21:56                 ` Andrew Lunn
2015-02-26  0:53                 ` Scott Feldman
2015-02-26  4:21                   ` Andy Gospodarek
2015-02-26  6:47                     ` Jiri Pirko
2015-02-26  7:14                       ` B Viswanath
2015-02-26 14:13                       ` Andy Gospodarek
2015-02-26 14:19                         ` Scott Feldman
2015-02-26 14:44                           ` Jiri Pirko
2015-02-27 22:21                             ` David Miller
2015-02-26 17:52                           ` Florian Fainelli
2015-02-26 17:51                       ` Florian Fainelli
2015-02-25  6:44       ` Rafał Miłecki
2015-02-24 22:48 ` Florian Fainelli
2015-02-24 22:56   ` Rafał Miłecki
2015-02-24 22:59     ` Florian Fainelli
2015-02-25  2:10   ` David Miller

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=20150225080751.GC2039@nanopsycho.orion \
    --to=jiri@resnulli.us \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=gospo@cumulusnetworks.com \
    --cc=hauke@hauke-m.de \
    --cc=jogo@openwrt.org \
    --cc=nbd@openwrt.org \
    --cc=netdev@vger.kernel.org \
    --cc=zajec5@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 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).