From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: netdev@vger.kernel.org, idosch@mellanox.com, eladr@mellanox.com,
yotamg@mellanox.com, nogahf@mellanox.com, ogerlitz@mellanox.com,
roopa@cumulusnetworks.com, nikolay@cumulusnetworks.com,
gospo@cumulusnetworks.com, ast@plumgrid.com, edumazet@google.com,
f.fainelli@gmail.com, dsa@cumulusnetworks.com,
daniel@iogearbox.net, vivien.didelot@savoirfairelinux.com
Subject: Re: [patch net-next 0/5] mlxsw: Introduce support for offload forward mark
Date: Fri, 26 Aug 2016 13:14:05 -0700 (PDT) [thread overview]
Message-ID: <20160826.131405.2118666831071325872.davem@davemloft.net> (raw)
In-Reply-To: <1472143360-15796-1-git-send-email-jiri@resnulli.us>
From: Jiri Pirko <jiri@resnulli.us>
Date: Thu, 25 Aug 2016 18:42:35 +0200
> Ido says:
> This patchset enables the forwarding of certain control packets by the
> device instead of relying on the CPU to do the forwarding.
>
> The first two patches simplify the current switchdev offload forward
> infrastructure and make it usable for stacked devices. This is done by
> moving the packet and port marking to the bridge driver instead of the
> switch driver.
>
> Patches 3-5 add the mlxsw specific bits to support the forward mark.
Series applied, thanks.
prev parent reply other threads:[~2016-08-26 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 16:42 [patch net-next 0/5] mlxsw: Introduce support for offload forward mark Jiri Pirko
2016-08-25 16:42 ` [patch net-next 1/5] switchdev: Support parent ID comparison for stacked devices Jiri Pirko
2016-08-25 16:42 ` [patch net-next 2/5] bridge: switchdev: Add forward mark support " Jiri Pirko
2016-08-25 16:42 ` [patch net-next 3/5] mlxsw: spectrum: Simplify traps definition Jiri Pirko
2016-08-25 16:42 ` [patch net-next 4/5] mlxsw: spectrum: Allow different traps to have different actions Jiri Pirko
2016-08-25 16:42 ` [patch net-next 5/5] mlxsw: spectrum: Mirror certain packets to CPU Jiri Pirko
2016-08-26 20:14 ` David Miller [this message]
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=20160826.131405.2118666831071325872.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=dsa@cumulusnetworks.com \
--cc=edumazet@google.com \
--cc=eladr@mellanox.com \
--cc=f.fainelli@gmail.com \
--cc=gospo@cumulusnetworks.com \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=nogahf@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=roopa@cumulusnetworks.com \
--cc=vivien.didelot@savoirfairelinux.com \
--cc=yotamg@mellanox.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).