linux-stable.git/include/linux/netdevice.h, branch v3.19.3

netdevice: Add missing parentheses in macro

2015-01-14T21:34:41+00:00

For example, one could conceivably call
	for_each_netdev_in_bond_rcu(condition ? bond1 : bond2, slave)
and get an unexpected result.

Signed-off-by: Benjamin Poirier 
Signed-off-by: David S. Miller

net: Corrected the comment describing the ndo operations to reflect the actual prototype for couple of operations

2015-01-13T19:03:42+00:00

Corrected the comment describing the ndo operations to
reflect the actual prototype for couple of operations

Signed-off-by: B Viswanath 
Signed-off-by: David S. Miller

net: Generalize ndo_gso_check to ndo_features_check

2014-12-26T22:20:56+00:00

GSO isn't the only offload feature with restrictions that
potentially can't be expressed with the current features mechanism.
Checksum is another although it's a general issue that could in
theory apply to anything. Even if it may be possible to
implement these restrictions in other ways, it can result in
duplicate code or inefficient per-packet behavior.

This generalizes ndo_gso_check so that drivers can remove any
features that don't make sense for a given packet, similar to
netif_skb_features(). It also converts existing driver
restrictions to the new format, completing the work that was
done to support tunnel protocols since the issues apply to
checksums as well.

By actually removing features from the set that are used to do
offloading, it solves another problem with the existing
interface. In these cases, GSO would run with the original set
of features and not do anything because it appears that
segmentation is not required.

CC: Tom Herbert 
CC: Joe Stringer 
CC: Eric Dumazet 
CC: Hayes Wang 
Signed-off-by: Jesse Gross 
Acked-by:  Tom Herbert 
Fixes: 04ffcb255f22 ("net: Add ndo_gso_check")
Tested-by: Hayes Wang 
Signed-off-by: David S. Miller

ipvlan: move the device check function into netdevice.h

2014-12-09T21:10:06+00:00

Move the port check [ipvlan_dev_master()] and device check
[ipvlan_dev_slave()] functions to netdevice.h and rename them
netif_is_ipvlan_port() and netif_is_ipvlan() resp. to be
consistent with macvlan api naming.

Signed-off-by: Mahesh Bandewar 
Signed-off-by: David S. Miller

netdevice: Add a function to check macvlan port

2014-12-09T21:10:06+00:00

Similar to a check for macvlan device, netif_is_macvlan(), add
another function to check if a device is used as macvlan port.

Signed-off-by: Mahesh Bandewar 
Signed-off-by: David S. Miller

bridge: call netdev_sw_port_stp_update when bridge port STP status changes

2014-12-03T04:01:22+00:00

To notify switch driver of change in STP state of bridge port, add new
.ndo op and provide switchdev wrapper func to call ndo op. Use it in bridge
code then.

Signed-off-by: Scott Feldman 
Signed-off-by: Jiri Pirko 
Signed-off-by: Andy Gospodarek 
Acked-by: Thomas Graf 
Acked-by: Florian Fainelli 
Signed-off-by: David S. Miller

net: introduce generic switch devices support

2014-12-03T04:01:20+00:00

The goal of this is to provide a possibility to support various switch
chips. Drivers should implement relevant ndos to do so. Now there is
only one ndo defined:
- for getting physical switch id is in place.

Note that user can use random port netdevice to access the switch.

Signed-off-by: Jiri Pirko 
Reviewed-by: Thomas Graf 
Acked-by: Andy Gospodarek 
Signed-off-by: David S. Miller

net: rename netdev_phys_port_id to more generic name

2014-12-03T04:01:19+00:00

So this can be reused for identification of other "items" as well.

Signed-off-by: Jiri Pirko 
Reviewed-by: Thomas Graf 
Acked-by: John Fastabend 
Acked-by: Andy Gospodarek 
Acked-by: Jamal Hadi Salim 
Signed-off-by: David S. Miller

net: make vid as a parameter for ndo_fdb_add/ndo_fdb_del

2014-12-03T04:01:18+00:00

Do the work of parsing NDA_VLAN directly in rtnetlink code, pass simple
u16 vid to drivers from there.

Signed-off-by: Jiri Pirko 
Acked-by: Andy Gospodarek 
Acked-by: Jamal Hadi Salim 
Acked-by: John Fastabend 
Signed-off-by: David S. Miller

ipvlan: Initial check-in of the IPVLAN driver.

2014-11-24T20:29:18+00:00

This driver is very similar to the macvlan driver except that it
uses L3 on the frame to determine the logical interface while
functioning as packet dispatcher. It inherits L2 of the master
device hence the packets on wire will have the same L2 for all
the packets originating from all virtual devices off of the same
master device.

This driver was developed keeping the namespace use-case in
mind. Hence most of the examples given here take that as the
base setup where main-device belongs to the default-ns and
virtual devices are assigned to the additional namespaces.

The device operates in two different modes and the difference
in these two modes in primarily in the TX side.

(a) L2 mode : In this mode, the device behaves as a L2 device.
TX processing upto L2 happens on the stack of the virtual device
associated with (namespace). Packets are switched after that
into the main device (default-ns) and queued for xmit.

RX processing is simple and all multicast, broadcast (if
applicable), and unicast belonging to the address(es) are
delivered to the virtual devices.

(b) L3 mode : In this mode, the device behaves like a L3 device.
TX processing upto L3 happens on the stack of the virtual device
associated with (namespace). Packets are switched to the
main-device (default-ns) for the L2 processing. Hence the routing
table of the default-ns will be used in this mode.

RX processins is somewhat similar to the L2 mode except that in
this mode only Unicast packets are delivered to the virtual device
while main-dev will handle all other packets.

The devices can be added using the "ip" command from the iproute2
package -

	ip link add link   type ipvlan mode [ l2 | l3 ]

Signed-off-by: Mahesh Bandewar 
Cc: Eric Dumazet 
Cc: Maciej Żenczykowski 
Cc: Laurent Chavey 
Cc: Tim Hockin 
Cc: Brandon Philips 
Cc: Pavel Emelianov 
Signed-off-by: David S. Miller