Searched refs:SAN (Results 1 – 9 of 9) sorted by relevance
29 setup_ns RB PEER SAN34 ip link add rb_il netns "$RB" type veth peer name san_il netns "$SAN"41 ip -n "$SAN" link set san_il up42 ip -n "$SAN" addr add 100.64.0.51/24 dev san_il57 san_mac=$(ip -n "$SAN" -br link show san_il | awk '{print $3}')62 do_ping "$SAN" 100.64.0.278 ip netns exec "$SAN" ping -i 0.2 -q 100.64.0.2 >/dev/null 2>&1 &
11 The Surface ACPI Notify (SAN) device provides the bridge between ACPI and24 A client to the SAN interface can be linked as consumer to the SAN device26 receiving dGPU events does not miss any events due to the SAN interface not27 being set up as this forces the client driver to unbind once the SAN driver
28 can have Singly Attached Nodes (SAN) such as PC, printer, bridges
9 transparent. Devices discovered on the SAN will be registered and unregistered
43 Surface ACPI Notify (SAN) driver for Microsoft Surface devices.45 This driver provides support for the ACPI interface (called SAN) of
36 SAN), translating ACPI generic serial bus write-/read-accesses to SAM
275 SAN/ACPI via the ``SNC`` flag).
767 echo Looking for K[AC]SAN files to compress: `date` > "$tdir/log-xz" 2>&1
1700 { 0xB1, 0x53 }, /* GEORGIAN CAPITAL LETTER SAN -> 'S' */1726 { 0xE1, 0x73 }, /* GEORGIAN LETTER SAN -> 's' */