From: Andrew Lunn <andrew@lunn.ch>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: sfeldma@gmail.com, netdev@vger.kernel.org, jiri@resnulli.us,
roopa@cumulusnetworks.com, simon.horman@netronome.com,
nicolas.dichtel@6wind.com, vivien.didelot@savoirfairelinux.com,
linux@roeck-us.net
Subject: Re: [PATCH net-next v3 0/5] switchdev: avoid duplicate packet forwarding
Date: Mon, 20 Jul 2015 20:08:55 +0200 [thread overview]
Message-ID: <20150720180855.GH14842@lunn.ch> (raw)
In-Reply-To: <55AD3687.9010002@gmail.com>
> This looks good to me, and it looks like this is also relevant for
> DSA-driven switches, however I am not exactly clear on how we could
> potentially use this on such switches.
>
> For Broadcom tags, there is a reason code forwarded along with the tag
> making it to the CPU, and the "mirror" bit sounds like something that
> should dictate whether we should be setting the fwd_mark or not.
>
> What does it look like on Marvell switches?
Hi Florian
There are some bits indicating some status information. But these are
more to do with BDPU, IGMP/MLD and ARP.
I've not yet had time to dig into the details here. I suspect the D in
DSA is going to make this very interesting.
Andrew
next prev parent reply other threads:[~2015-07-20 18:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 1:24 [PATCH net-next v3 0/5] switchdev: avoid duplicate packet forwarding sfeldma
2015-07-19 1:24 ` [PATCH net-next v3 1/5] net: don't reforward packets already forwarded by offload device sfeldma
2015-07-20 7:21 ` Nicolas Dichtel
2015-07-19 1:24 ` [PATCH net-next v3 2/5] net: add phys ID compare helper to test if two IDs are the same sfeldma
2015-07-19 1:24 ` [PATCH net-next v3 3/5] switchdev: add offload_fwd_mark generator helper sfeldma
2015-07-19 1:24 ` [PATCH net-next v3 4/5] rocker: add offload_fwd_mark support sfeldma
2015-07-19 1:24 ` [PATCH net-next v3 5/5] switchdev: update documentation for offload_fwd_mark sfeldma
2015-07-20 17:57 ` [PATCH net-next v3 0/5] switchdev: avoid duplicate packet forwarding Florian Fainelli
2015-07-20 18:08 ` Andrew Lunn [this message]
2015-07-21 1:33 ` 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=20150720180855.GH14842@lunn.ch \
--to=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=jiri@resnulli.us \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@gmail.com \
--cc=simon.horman@netronome.com \
--cc=vivien.didelot@savoirfairelinux.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).