Home
last modified time | relevance | path

Searched refs:permanent (Results 1 – 25 of 80) sorted by relevance

1234

/linux/tools/testing/selftests/net/forwarding/
A Dbridge_mdb.sh202 bridge mdb add dev br0 port $swp1 $grp_key permanent vid 10
210 bridge mdb del dev br0 port $swp1 $grp_key permanent vid 10
226 bridge mdb add dev br0 port $swp1 $grp_key permanent
232 bridge mdb del dev br0 port $swp1 $grp_key permanent
260 bridge mdb add dev br0 port $swp1 $grp_key permanent vid \
674 permanent vid 10 &> /dev/null
678 permanent vid 10 &> /dev/null
881 bridge mdb flush dev br0 permanent
915 bridge mdb flush dev br0 permanent
927 bridge mdb flush dev br0 permanent
[all …]
A Dmirror_gre_bridge_1q.sh94 nud permanent dev br1
102 nud permanent dev br1
A Dmirror_gre_bridge_1d.sh98 nud permanent dev br2
106 nud permanent dev br2
A Dmirror_gre_bridge_1d_vlan.sh96 nud permanent dev br2
103 nud permanent dev br2
A Dbridge_mdb_host.sh91 do_mdb_add_del $TEST_GROUP_MAC permanent
A Dbridge_mdb_port_down.sh20 bridge mdb add dev br0 port "$swp2" grp $TEST_GROUP permanent 2>/dev/null
/linux/tools/testing/selftests/net/
A Dtest_vxlan_fdb_changelink.sh21 bridge fdb ap dev vx 00:00:00:00:00:00 dst 192.0.2.20 self permanent
22 bridge fdb ap dev vx 00:00:00:00:00:00 dst 192.0.2.30 self permanent
A Dtest_vxlan_under_vrf.sh116 bridge -netns $hv_1 fdb add 00:00:00:00:00:00 dev vxlan0 dst 172.16.0.2 self permanent
117 bridge -netns $hv_2 fdb add 00:00:00:00:00:00 dev vxlan0 dst 172.16.0.1 self permanent
/linux/Documentation/networking/devlink/
A Dnfp.rst18 - permanent
20 - permanent
/linux/arch/arm/boot/dts/marvell/
A Dkirkwood-t5325.dts101 label = "permanent u-boot env";
106 label = "permanent u-boot env";
/linux/Documentation/networking/device_drivers/ethernet/ti/
A Dam65_nuss_cpsw_switchdev.rst120 bridge mdb add dev br0 port sw0p1 grp 239.1.1.1 permanent vid 100
121 bridge mdb add dev br0 port sw0p1 grp 239.1.1.1 permanent <---- Add on all VLANs
A Dcpsw_switchdev.rst170 bridge mdb add dev br0 port sw0p1 grp 239.1.1.1 permanent vid 100
171 bridge mdb add dev br0 port sw0p1 grp 239.1.1.1 permanent <---- Add on all VLANs
/linux/Documentation/networking/
A Dswitchdev.rst242 52:54:00:12:35:01 dev sw1p1 master br0 permanent
245 52:54:00:12:35:02 dev sw1p2 master br0 permanent
248 33:33:00:00:00:01 dev eth0 self permanent
249 01:00:5e:00:00:01 dev eth0 self permanent
250 33:33:ff:00:00:00 dev eth0 self permanent
251 01:80:c2:00:00:0e dev eth0 self permanent
252 33:33:00:00:00:01 dev br0 self permanent
253 01:00:5e:00:00:01 dev br0 self permanent
254 33:33:ff:12:35:01 dev br0 self permanent
/linux/Documentation/filesystems/xfs/
A Dxfs-delayed-logging-design.rst58 reservation they take. These are known as "one shot" and "permanent"
64 place. This means that permanent transactions can be used for one-shot
65 modifications, but one-shot reservations cannot be used for permanent
81 In contrast, a permanent transaction is made up of multiple linked individual
111 It is important to note that a series of rolling transactions in a permanent
188 While a permanent transaction can get by with a single unit of space
199 chain. Each time a permanent transaction rolls, it consumes an entire unit
202 Hence when the permanent transaction is first allocated, the log space
253 forwards progress guarantees that rolling permanent transactions require.
284 Code using permanent reservations must always log the items they hold
[all …]
/linux/fs/xfs/
A Dxfs_log.h143 struct xlog_ticket **ticket, bool permanent);
A Dxfs_trans.c176 bool permanent = false; in xfs_trans_reserve() local
185 permanent = true; in xfs_trans_reserve()
197 &tp->t_ticket, permanent); in xfs_trans_reserve()
A Dxfs_log_priv.h506 int count, bool permanent);
/linux/Documentation/netlink/specs/
A Drt_addr.yaml68 name: permanent
/linux/Documentation/fb/
A Dmetronomefb.rst32 a possibility that it could have some permanent effects on the display media.
/linux/Documentation/input/devices/
A Dbcm5974.rst65 a more permanent home at bitmath.org [#f2]_.
/linux/tools/testing/selftests/drivers/net/mlxsw/
A Ddevlink_trap_control.sh474 ip -4 neigh add 192.0.2.3 lladdr 00:11:22:33:44:55 nud permanent \
476 ip -6 neigh add 2001:db8:1::3 lladdr 00:11:22:33:44:55 nud permanent \
/linux/Documentation/devicetree/bindings/powerpc/fsl/
A Dpmc.txt52 hardware does not have DEVDISR2) upon a request for permanent device
/linux/net/can/
A DKconfig38 sending of RTR frames, and cyclic CAN messages without permanent user
/linux/Documentation/userspace-api/media/drivers/
A Dimx-uapi.rst38 permanent split image (one frame contains lines from two consecutive
/linux/Documentation/PCI/
A Dpci-error-recovery.rst301 will typically report a "permanent failure" in such a case. The
350 A "permanent failure" has occurred, and the platform cannot recover
361 permanent failure in some way. If the device is hotplug-capable,
363 Note, however, not all failures are truly "permanent". Some are

Completed in 42 milliseconds

1234