Lines Matching refs:driver

1 Ethernet switch device driver model (switchdev)
7 The Ethernet switch device driver model (switchdev) is an in-kernel driver
33                      |         Switch driver         |  |    mgmt   |         
34                      |        (this document)        |  |   driver  |         
67 Use "depends NET_SWITCHDEV" in driver's Kconfig to ensure switchdev model
68 support is built for driver.
74 On switchdev driver initialization, the driver will allocate and register a
85 port netdevs.  All of the switchdev driver ops are netdev ops or switchdev ops.
87 A switch management port is outside the scope of the switchdev driver model.
89 is loaded with a different driver, such as a NIC driver, on the management port
97 Hard-coding of kernel netdev names within the driver is discouraged; let the
107 SUBSYSTEM=="net", ACTION=="add", DRIVER="<driver>", ATTR{phys_port_name}!="", \
117 The switchdev driver must implement the switchdev op switchdev_port_attr_get
131 If the switchdev driver (and device) only supports offloading of the default
132 network namespace (netns), the driver should set this feature flag to prevent
134 driver/device would not set this flag and be responsible for partitioning
147 tools such as the bridge driver, the bonding/team drivers, and netlink-based
150 The switchdev driver can know a particular port's position in the topology by
153 the bond's upper master will change.  And so on.  The driver will track such
164 To offloading L2 bridging, the switchdev driver/device should support:
174 The switchdev driver should implement ndo_fdb_add, ndo_fdb_del and ndo_fdb_dump
180 The driver should use the helper switchdev_port_fdb_xxx ops for ndo_fdb_xxx
196 and notify the switch driver of the mac/vlan/port tuples.  The switch driver,
197 in turn, will notify the bridge driver using the switchdev notifier call:
203 SWITCHDEV_FDB_ADD, the bridge driver will install the FDB entry into the
235 To support learning and learning_sync port attributes, the driver implements
237 SWITCHDEV_ATTR_PORT_ID_BRIDGE_FLAGS. The driver should initialize the attributes
244 the responsibility of the port driver/device to age out these entries.  If the
246 driver which in turn will notify the bridge with SWITCHDEV_FDB_DEL.  If the
247 device does not support ageing, the driver can simulate ageing using a
249 notified to the bridge using SWITCHDEV_FDB_DEL.  See rocker driver for
250 example of driver running ageing timer.
252 To keep an NTF_EXT_LEARNED entry "alive", the driver should refresh the FDB
254 notification will reset the FDB entry's last-used time to now.  The driver
262 bridge driver maintains the STP state for ports, and will notify the switch
263 driver of STP state change on a port using the switchdev op
266 State is one of BR_STATE_*.  The switch driver can use STP state updates to
280 current STP state.  The switch driver, knowing which ports are within which
282 be sent to the port netdev for processing by the bridge driver.  The
286 To avoid duplicate packets, the device/driver should mark a packet as already
292 The driver can use switchdev_port_fwd_mark_set() to set a globally unique mark
297 packets up to the bridge driver for flooding.  This is not ideal as the number
318 To program the device, the driver implements support for
341 driver is not called to add/modify/delete the FIB entry.
368 arp_tbl neighbor table.  To resolve the routes nexthop gateways, the driver
370 driver's rocker_port_ipv4_resolve() for an example.
372 The driver can monitor for updates to arp_tbl using the netevent notifier
374 for the routes as arp_tbl updates.  The driver implements ndo_neigh_destroy
388 The object created by a driver in "prepare" phase and it is queued up by:
390 During the "commit" phase, the driver gets the object by: