From: Andrew Lunn <andrew@lunn.ch>
To: Murali Karicheri <m-karicheri2@ti.com>
Cc: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Roger Quadros <rogerq@ti.com>,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: Re: DSA vs. SWTICHDEV ?
Date: Thu, 1 Dec 2016 18:31:00 +0100 [thread overview]
Message-ID: <20161201173100.GG21887@lunn.ch> (raw)
In-Reply-To: <584054C4.1010809@ti.com>
Hi Murali
> 2. Switch mode where it implements a simple Ethernet switch. Currently
> it doesn't have address learning capability, but in future it
> can.
If it does not have address learning capabilities, does it act like a
plain old hub? What comes in one port goes out all others?
Or can you do the learning in software on the host and program tables,
which the hardware then uses?
> 3. Switch with HSR/PRP offload where it provides HSR/PRP protocol
> support and cut through switch.
>
> So a device need to function in one of the modes. A a regular Ethernet
> driver that provides two network devices, one per port, and switchdev
> for each physical port (in switch mode) will look ideal in this case.
Yes, this seems the right model to use.
Andrew
next prev parent reply other threads:[~2016-12-01 17:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 8:50 DSA vs. SWTICHDEV ? Joakim Tjernlund
2016-11-30 13:52 ` Andrew Lunn
2016-11-30 14:30 ` Joakim Tjernlund
2016-11-30 15:25 ` Andrew Lunn
2016-11-30 16:35 ` Joakim Tjernlund
2016-11-30 16:55 ` Andrew Lunn
2016-11-30 17:44 ` Joakim Tjernlund
2016-11-30 18:09 ` Andrew Lunn
2016-11-30 20:43 ` Jiri Pirko
2016-11-30 18:10 ` Florian Fainelli
2016-11-30 18:44 ` Joakim Tjernlund
2016-11-30 19:39 ` Florian Fainelli
2016-12-01 16:50 ` Murali Karicheri
2016-12-01 17:31 ` Andrew Lunn [this message]
2016-12-01 21:38 ` Murali Karicheri
2016-12-02 15:38 ` Andrew Lunn
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=20161201173100.GG21887@lunn.ch \
--to=andrew@lunn.ch \
--cc=Joakim.Tjernlund@infinera.com \
--cc=grygorii.strashko@ti.com \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=rogerq@ti.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).