From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, andrew@lunn.ch, linux@roeck-us.net,
jiri@resnulli.us, sfeldma@gmail.com,
Florian Fainelli <f.fainelli@gmail.com>
Subject: [PATCH RFC 0/5] net: L2 only interfaces
Date: Tue, 25 Aug 2015 15:50:10 -0700 [thread overview]
Message-ID: <1440543015-14693-1-git-send-email-f.fainelli@gmail.com> (raw)
Hi all,
This patch series implements a L2 only interface concept which basically denies
any kind of IP address configuration on these interfaces, but still allows them
to be used as configuration end-points to keep using ethtool and friends.
A cleaner approach might be to finally come up with the concept of net_port
which a net_device would be a superset of, but this still raises tons of
questions as to whether we should be modifying userland tools to be able to
configure/query these interfaces. During all the switch talks/discussions last
year, it seemed to me like th L2-only interface is closest we have to a
"network port".
Comments, flames, flying tomatoes welcome!
Florian Fainelli (5):
net: add IFF_L2_ONLY flag
net: ipv4: Skip in_dev initialization for IFF_L2_ONLY interfaces
net: ipv6: Skip in6_dev initialization for IFF_L2_ONLY interfaces
net: dsa: Flag slave network devices with IFF_L2_ONLY
net: dsa: bcm_sf2: Allow disabling tagging protocol
drivers/net/dsa/bcm_sf2.c | 16 +++++++++++++---
include/uapi/linux/if.h | 5 ++++-
net/dsa/slave.c | 1 +
net/ipv4/devinet.c | 3 +++
net/ipv6/addrconf.c | 4 ++++
5 files changed, 25 insertions(+), 4 deletions(-)
--
2.1.0
next reply other threads:[~2015-08-25 22:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 22:50 Florian Fainelli [this message]
2015-08-25 22:50 ` [PATCH RFC 1/5] net: add IFF_L2_ONLY flag Florian Fainelli
2015-08-25 22:50 ` [PATCH RFC 2/5] net: ipv4: Skip in_dev initialization for IFF_L2_ONLY interfaces Florian Fainelli
2015-08-25 22:50 ` [PATCH RFC 3/5] net: ipv6: Skip in6_dev " Florian Fainelli
2015-08-25 22:50 ` [PATCH RFC 4/5] net: dsa: Flag slave network devices with IFF_L2_ONLY Florian Fainelli
2015-08-25 22:50 ` [PATCH RFC 5/5] net: dsa: bcm_sf2: Allow disabling tagging protocol Florian Fainelli
2015-08-26 0:09 ` David Miller
2015-08-25 23:20 ` [PATCH RFC 0/5] net: L2 only interfaces Alexei Starovoitov
2015-08-25 23:24 ` Florian Fainelli
2015-08-25 23:33 ` David Ahern
2015-09-01 17:07 ` Vivien Didelot
2015-08-25 23:24 ` Stephen Hemminger
2015-08-25 23:23 ` Florian Fainelli
2015-08-25 23:44 ` Sowmini Varadhan
2015-08-25 23:52 ` David Ahern
2015-08-26 0:05 ` Sowmini Varadhan
2015-08-26 0:12 ` David Miller
2015-08-26 4:24 ` Marcel Holtmann
2015-08-26 17:37 ` Florian Fainelli
2015-08-26 17:56 ` Marcel Holtmann
2015-08-26 17:32 ` Florian Fainelli
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=1440543015-14693-1-git-send-email-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=linux@roeck-us.net \
--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).