From: Simon Horman <simon.horman@netronome.com>
To: Jiri Pirko <jiri@resnulli.us>, Scott Feldman <sfeldma@gmail.com>
Cc: netdev@vger.kernel.org, Simon Horman <simon.horman@netronome.com>
Subject: [PATCH/RFC net-next 0/4] Allow use of rocker ports without bridging
Date: Mon, 13 Apr 2015 15:47:53 +0900 [thread overview]
Message-ID: <1428907677-27204-1-git-send-email-simon.horman@netronome.com> (raw)
Hi,
this short series attempts to allow rocker ports to be used when they
are not attached to a bridge. It attempts to make use of flow entries
in a rocker switch where appropriate and otherwise forwards packets up
to the kernel for processing.
I have lightly tested this series using unicast IPv4 (mainly ARP and ping).
Simon Horman (4):
rocker: add helper for setting untagged VLAN
rocker: set untagged VLAN when opening port
rocker: forward packets to CPU when a port not bridged
rocker: allow forwarding of IPv4 by unicast routing table
drivers/net/ethernet/rocker/rocker.c | 138 ++++++++++++++++++++++++++++-------
1 file changed, 110 insertions(+), 28 deletions(-)
--
2.1.4
next reply other threads:[~2015-04-13 6:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 6:47 Simon Horman [this message]
2015-04-13 6:47 ` [PATCH/RFC net-next 1/4] rocker: add helper for setting untagged VLAN Simon Horman
2015-04-13 6:47 ` [PATCH/RFC net-next 2/4] rocker: set untagged VLAN when opening port Simon Horman
2015-04-13 6:47 ` [PATCH/RFC net-next 3/4] rocker: forward packets to CPU when a port not bridged Simon Horman
2015-04-13 6:47 ` [PATCH/RFC net-next 4/4] rocker: allow forwarding of IPv4 by unicast routing table Simon Horman
2015-04-13 14:59 ` [PATCH/RFC net-next 0/4] Allow use of rocker ports without bridging Scott Feldman
2015-04-13 15:43 ` Scott Feldman
2015-04-14 7:11 ` Simon Horman
2015-04-14 7:23 ` Scott Feldman
2015-04-14 8:02 ` Simon Horman
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=1428907677-27204-1-git-send-email-simon.horman@netronome.com \
--to=simon.horman@netronome.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=sfeldma@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).