From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, davem@davemloft.net, andrew@lunn.ch,
linux@roeck-us.net, jiri@resnulli.us, sfeldma@gmail.com,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Subject: Re: [PATCH RFC 0/5] net: L2 only interfaces
Date: Tue, 1 Sep 2015 13:07:15 -0400 [thread overview]
Message-ID: <20150901170715.GA5919@ketchup.mtl.sfl> (raw)
In-Reply-To: <20150825232021.GA8482@Alexeis-MacBook-Pro-2.local>
Hi Florian, All,
On Aug. Tuesday 25 (35) 04:20 PM, Alexei Starovoitov wrote:
> On Tue, Aug 25, 2015 at 03:50:10PM -0700, Florian Fainelli wrote:
> > 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
>
> interesting idea! Do you know how kernel/iproute2 will react to lack of in_dev?
> No crashes I'm assuming, but what kind of errors are thrown?
> imo great first step to have lightweight netdevs. +1 for 'net_port' in the future.
Lightening net_device with a new inner net_port structure seems like a
great idea to register and expose L2 only interfaces.
DSA would get benefit from this too, as we could finally expose CPU and
DSA ports. We'll then be able to use standard tools to configure them
(e.g. speed/duplex), and allow fine-grained control of bridging: we may
want to explicitly include or exclude these ports in bridges or VLANs.
Same goes for the support of basic switches (home routers).
A new iproute2 command or additional command line flags can be added
later to explicitly access them from userspace. In the meantime,
ifconfig and such would transparently configure (net_device)->port.
Thanks,
-v
next prev parent reply other threads:[~2015-09-01 17:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 22:50 [PATCH RFC 0/5] net: L2 only interfaces Florian Fainelli
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 [this message]
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=20150901170715.GA5919@ketchup.mtl.sfl \
--to=vivien.didelot@savoirfairelinux.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.