1menuconfig NET_TEAM 2 tristate "Ethernet team driver support" 3 ---help--- 4 This allows one to create virtual interfaces that teams together 5 multiple ethernet devices. 6 7 Team devices can be added using the "ip" command from the 8 iproute2 package: 9 10 "ip link add link [ address MAC ] [ NAME ] type team" 11 12 To compile this driver as a module, choose M here: the module 13 will be called team. 14 15if NET_TEAM 16 17config NET_TEAM_MODE_BROADCAST 18 tristate "Broadcast mode support" 19 depends on NET_TEAM 20 ---help--- 21 Basic mode where packets are transmitted always by all suitable ports. 22 23 All added ports are setup to have team's device address. 24 25 To compile this team mode as a module, choose M here: the module 26 will be called team_mode_broadcast. 27 28config NET_TEAM_MODE_ROUNDROBIN 29 tristate "Round-robin mode support" 30 depends on NET_TEAM 31 ---help--- 32 Basic mode where port used for transmitting packets is selected in 33 round-robin fashion using packet counter. 34 35 All added ports are setup to have team's device address. 36 37 To compile this team mode as a module, choose M here: the module 38 will be called team_mode_roundrobin. 39 40config NET_TEAM_MODE_ACTIVEBACKUP 41 tristate "Active-backup mode support" 42 depends on NET_TEAM 43 ---help--- 44 Only one port is active at a time and the rest of ports are used 45 for backup. 46 47 Mac addresses of ports are not modified. Userspace is responsible 48 to do so. 49 50 To compile this team mode as a module, choose M here: the module 51 will be called team_mode_activebackup. 52 53config NET_TEAM_MODE_LOADBALANCE 54 tristate "Load-balance mode support" 55 depends on NET_TEAM 56 ---help--- 57 This mode provides load balancing functionality. Tx port selection 58 is done using BPF function set up from userspace (bpf_hash_func 59 option) 60 61 To compile this team mode as a module, choose M here: the module 62 will be called team_mode_loadbalance. 63 64endif # NET_TEAM 65