Home
last modified time | relevance | path

Searched refs:IP (Results 1 – 25 of 535) sorted by relevance

12345678910>>...22

/Linux-v5.4/tools/testing/selftests/net/
Dfib_nexthops.sh148 IP="ip -netns me"
150 $IP li add veth1 type veth peer name veth2
151 $IP li set veth1 up
152 $IP addr add 172.16.1.1/24 dev veth1
153 $IP -6 addr add 2001:db8:91::1/64 dev veth1
155 $IP li add veth3 type veth peer name veth4
156 $IP li set veth3 up
157 $IP addr add 172.16.2.1/24 dev veth3
158 $IP -6 addr add 2001:db8:92::1/64 dev veth3
160 $IP li set veth2 netns peer up
[all …]
Dfib_tests.sh17 IP="ip -netns ns1"
56 $IP link set dev lo up
60 $IP link add dummy0 type dummy
61 $IP link set dev dummy0 up
62 $IP address add 198.51.100.1/24 dev dummy0
63 $IP -6 address add 2001:db8:1::1/64 dev dummy0
70 $IP link del dev dummy0 &> /dev/null
80 addr=$($IP -6 -br addr show dev ${dev} | \
105 $IP route get fibmatch 198.51.100.2 &> /dev/null
107 $IP -6 route get fibmatch 2001:db8:1::2 &> /dev/null
[all …]
Dfib_rule_tests.sh9 IP="ip -netns testns"
55 $IP link set dev lo up
57 $IP link add dummy0 type dummy
58 $IP link set dev dummy0 up
59 $IP address add $DEV_ADDR/24 dev dummy0
60 $IP -6 address add $DEV_ADDR6/64 dev dummy0
67 $IP link del dev dummy0 &> /dev/null
90 $IP -6 rule del $1
96 pref=$($IP -6 rule show | grep "$1 lookup $TABLE" | cut -d ":" -f 1)
97 $IP -6 rule del pref $pref
[all …]
Dmsg_zerocopy.sh40 readonly IP="$1"
47 if [[ "${IP}" == "4" ]]; then
50 elif [[ "${IP}" == "6" ]]; then
54 echo "Invalid IP version ${IP}"
113 echo "ipv${IP} ${TXMODE} ${ARGS}"
114 …ip netns exec "${NS2}" "${BIN}" "-${IP}" -i "${DEV}" -t 2 -C 2 -S "${SADDR}" -D "${DADDR}" ${ARGS}…
116 …ip netns exec "${NS1}" "${BIN}" "-${IP}" -i "${DEV}" -t 1 -C 3 -S "${SADDR}" -D "${DADDR}" ${ARGS}…
/Linux-v5.4/samples/bpf/
Dtc_l2_redirect.sh5 [[ -z $IP ]] && IP='ip'
16 $IP netns add ns1
17 $IP netns add ns2
18 $IP link add ve1 type veth peer name vens1
19 $IP link add ve2 type veth peer name vens2
20 $IP link set dev ve1 up
21 $IP link set dev ve2 up
22 $IP link set dev ve1 mtu 1500
23 $IP link set dev ve2 mtu 1500
24 $IP link set dev vens1 netns ns1
[all …]
Dtest_cgrp2_tc.sh11 [ -z "$IP" ] && IP='ip'
74 $IP link add $HOST_IFC type veth peer name $NS_IFC || return $?
75 $IP link set dev $HOST_IFC up || return $?
78 $IP netns add ns || return $?
79 $IP link set dev $NS_IFC netns ns || return $?
80 $IP -n $NS link set dev $NS_IFC up || return $?
81 $IP netns exec $NS sysctl -q net.ipv6.conf.$NS_IFC.accept_dad=0
86 $IP netns del $NS
87 $IP link del $HOST_IFC
125 $IP netns
[all …]
/Linux-v5.4/include/trace/events/
Drandom.h12 TP_PROTO(int bytes, unsigned long IP),
14 TP_ARGS(bytes, IP),
18 __field(unsigned long, IP )
23 __entry->IP = IP;
27 __entry->bytes, (void *)__entry->IP)
31 TP_PROTO(const char *pool_name, int bytes, unsigned long IP),
33 TP_ARGS(pool_name, bytes, IP),
38 __field(unsigned long, IP )
44 __entry->IP = IP;
48 __entry->pool_name, __entry->bytes, (void *)__entry->IP)
[all …]
/Linux-v5.4/drivers/net/ethernet/intel/iavf/
Diavf_common.c573 IAVF_PTT(22, IP, IPV4, FRG, NONE, NONE, NOF, NONE, PAY3),
574 IAVF_PTT(23, IP, IPV4, NOF, NONE, NONE, NOF, NONE, PAY3),
575 IAVF_PTT(24, IP, IPV4, NOF, NONE, NONE, NOF, UDP, PAY4),
577 IAVF_PTT(26, IP, IPV4, NOF, NONE, NONE, NOF, TCP, PAY4),
578 IAVF_PTT(27, IP, IPV4, NOF, NONE, NONE, NOF, SCTP, PAY4),
579 IAVF_PTT(28, IP, IPV4, NOF, NONE, NONE, NOF, ICMP, PAY4),
582 IAVF_PTT(29, IP, IPV4, NOF, IP_IP, IPV4, FRG, NONE, PAY3),
583 IAVF_PTT(30, IP, IPV4, NOF, IP_IP, IPV4, NOF, NONE, PAY3),
584 IAVF_PTT(31, IP, IPV4, NOF, IP_IP, IPV4, NOF, UDP, PAY4),
586 IAVF_PTT(33, IP, IPV4, NOF, IP_IP, IPV4, NOF, TCP, PAY4),
[all …]
/Linux-v5.4/Documentation/networking/
Dipddp.txt2 AppleTalk-IP Decapsulation and AppleTalk-IP Encapsulation
9 AppleTalk-IP (IPDDP) is the method computers connected to AppleTalk
10 networks can use to communicate via IP. AppleTalk-IP is simply IP datagrams
14 IP over an AppleTalk network or you can provide IP gatewaying functions
17 You can currently encapsulate or decapsulate AppleTalk-IP on LocalTalk,
23 Compiling AppleTalk-IP Decapsulation/Encapsulation
26 AppleTalk-IP decapsulation needs to be compiled into your kernel. You
27 will need to turn on AppleTalk-IP driver support. Then you will need to
28 select ONE of the two options; IP to AppleTalk-IP encapsulation support or
29 AppleTalk-IP to IP decapsulation support. If you compile the driver
[all …]
Dgtp.txt12 tunneling User-IP payload between a mobile station (phone, modem)
23 technology-dependent protocol stack for transmitting the user IP
35 public internet, but can also be any private IP network (or even
36 theoretically some non-IP network like X.25).
47 able to decapsulate tunneled IP packets in the uplink originated by
48 the phone, and encapsulate raw IP packets received from the external
51 It *only* implements the so-called 'user plane', carrying the User-IP
111 on the inner (user) IP layer, or on the outer (transport) layer.
114 the User IP payload, nor for the outer IP layer. Patches or other
150 instance) per IP address. Tunnel Endpoint Identifier (TEID) are unique
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/mmc/
Drenesas,sdhi.txt5 "renesas,sdhi-sh73a0" - SDHI IP on SH73A0 SoC
6 "renesas,sdhi-r7s72100" - SDHI IP on R7S72100 SoC
7 "renesas,sdhi-r7s9210" - SDHI IP on R7S9210 SoC
8 "renesas,sdhi-r8a73a4" - SDHI IP on R8A73A4 SoC
9 "renesas,sdhi-r8a7740" - SDHI IP on R8A7740 SoC
10 "renesas,sdhi-r8a7743" - SDHI IP on R8A7743 SoC
11 "renesas,sdhi-r8a7744" - SDHI IP on R8A7744 SoC
12 "renesas,sdhi-r8a7745" - SDHI IP on R8A7745 SoC
13 "renesas,sdhi-r8a774a1" - SDHI IP on R8A774A1 SoC
14 "renesas,sdhi-r8a774c0" - SDHI IP on R8A774C0 SoC
[all …]
/Linux-v5.4/drivers/usb/usbip/
DKconfig4 tristate "USB/IP support"
8 This enables pushing USB packets over IP to allow remote
10 USB/IP core that is required by both drivers.
24 This enables the USB/IP virtual host controller driver,
31 int "Number of ports per USB/IP virtual host controller"
36 To increase number of ports available for USB/IP virtual
38 USB/IP virtual host controller.
41 int "Number of USB/IP virtual host controllers"
46 To increase number of ports available for USB/IP virtual
47 host controller driver, this defines number of USB/IP
[all …]
/Linux-v5.4/fs/jfs/
Djfs_btree.h50 #define BT_PAGE(IP, MP, TYPE, ROOT)\ argument
51 (BT_IS_ROOT(MP) ? (TYPE *)&JFS_IP(IP)->ROOT : (TYPE *)(MP)->data)
54 #define BT_GETPAGE(IP, BN, MP, TYPE, SIZE, P, RC, ROOT)\ argument
58 MP = (struct metapage *)&JFS_IP(IP)->bxflag;\
59 P = (TYPE *)&JFS_IP(IP)->ROOT;\
64 MP = read_metapage((IP), BN, SIZE, 1);\
76 #define BT_MARK_DIRTY(MP, IP)\ argument
79 mark_inode_dirty(IP);\
142 #define BT_GETSEARCH(IP, LEAF, BN, MP, TYPE, P, INDEX, ROOT)\ argument
149 P = (TYPE *)&JFS_IP(IP)->ROOT;\
/Linux-v5.4/Documentation/devicetree/bindings/sifive/
Dsifive-blocks-ip-versioning.txt1 DT compatible string versioning for SiFive open-source IP blocks
4 strings for open-source SiFive IP blocks. HDL for these IP blocks
9 IP block-specific DT compatible strings are contained within the HDL,
16 Until these IP blocks (or IP integration) support version
17 auto-discovery, the maintainers of these IP blocks intend to increment
19 interface to these IP blocks changes, or when the functionality of the
20 underlying IP blocks changes in a way that software should be aware of.
26 match on these IP block-specific compatible strings.
33 IP block-specific compatible string (such as "sifive,uart0") should
/Linux-v5.4/Documentation/devicetree/bindings/media/xilinx/
Dvideo.txt1 DT bindings for Xilinx video IP cores
4 Xilinx video IP cores process video streams by acting as video sinks and/or
8 Each video IP core is represented by an AMBA bus child node in the device
9 tree using bindings documented in this directory. Connections between the IP
18 The following properties are common to all Xilinx video IP cores.
21 AXI bus between video IP cores, using its VF code as defined in "AXI4-Stream
22 Video IP and System Design Guide" [UG934]. How the format relates to the IP
23 core is described in the IP core bindings documentation.
Dxlnx,video.txt1 Xilinx Video IP Pipeline (VIPP)
7 Xilinx video IP pipeline processes video streams through one or more Xilinx
8 video IP cores. Each video IP core is represented as documented in video.txt
9 and IP core specific documentation, xlnx,v-*.txt, in this directory. The DT
11 mappings between DMAs and the video IP cores.
/Linux-v5.4/Documentation/devicetree/bindings/clock/ti/
Ddra7-atl.txt3 The ATL IP is used to generate clock to be used to synchronize baseband and
4 audio codec. A single ATL IP provides four ATL clock instances sharing the same
16 Since the clock instances are part of a single IP this binding is used as a node
17 for the DT clock tree, the IP driver is needed to handle the actual configuration
18 of the IP.
27 Binding for the IP driver:
28 This binding is used to configure the IP driver which is going to handle the
29 configuration of the IP for the ATL clock instances.
33 - reg : base address for the ATL IP
75 /* binding for the IP */
/Linux-v5.4/Documentation/devicetree/bindings/gpu/
Dsamsung-rotator.txt5 * "samsung,s5pv210-rotator" for Rotator IP in S5PV210
6 * "samsung,exynos4210-rotator" for Rotator IP in Exynos4210
7 * "samsung,exynos4212-rotator" for Rotator IP in Exynos4212/4412
8 * "samsung,exynos5250-rotator" for Rotator IP in Exynos5250
10 - reg : Physical base address of the IP registers and length of memory
/Linux-v5.4/net/l2tp/
DKconfig20 L2TP is often used to tunnel PPP traffic over IP
21 tunnels. One IP tunnel may carry thousands of individual PPP
60 packet-oriented data network (e.g., over IP). L2TP, as
72 tristate "L2TP IP encapsulation for L2TPv3"
75 Support for L2TP-over-IP socket family.
78 L2TP frames, namely UDP and plain IP (without UDP). This
80 userspace L2TPv3 daemons may create L2TP/IP tunnel sockets
82 in IP packets, it used IP protocol number 115, so this port
99 across an IP network [RFC3931].
103 be used to assign an IP address to the local virtual
/Linux-v5.4/Documentation/networking/device_drivers/qualcomm/
Drmnet.txt8 IP mode. Physical transports include USB, HSIC, PCIe and IP accelerator.
12 multimedia messaging service (MMS) or IP media subsystem (IMS). Hardware sends
24 MAP header has the same endianness of the IP packet.
35 packets are standard IP packets.
70 packets and either ACK the MAP command or deliver the IP packet to the
73 MAP header|IP Packet|Optional padding|MAP header|IP Packet|Optional padding....
74 MAP header|IP Packet|Optional padding|MAP header|Command Packet|Optional pad...
/Linux-v5.4/drivers/staging/axis-fifo/
DKconfig3 # "Xilinx AXI-Stream FIFO IP core driver"
6 tristate "Xilinx AXI-Stream FIFO IP core driver"
9 This adds support for the Xilinx AXI-Stream FIFO IP core driver.
11 interface. The Xilinx AXI-Stream FIFO IP core can be used to interface
/Linux-v5.4/net/ipv4/
DKconfig3 # IP configuration
6 bool "IP: multicasting"
16 bool "IP: advanced router"
27 Note that your box can only act as a router if you enable IP
36 If you turn on IP forwarding, you should consider the rp_filter, which
40 so-called IP spoofing, however it can pose problems if you use
43 host which has several IP addresses on different interfaces. To turn
64 bool "IP: policy routing"
81 bool "IP: equal cost multipath"
93 bool "IP: verbose route monitoring"
[all …]
/Linux-v5.4/drivers/net/ethernet/intel/i40e/
Di40e_common.c601 I40E_PTT(22, IP, IPV4, FRG, NONE, NONE, NOF, NONE, PAY3),
602 I40E_PTT(23, IP, IPV4, NOF, NONE, NONE, NOF, NONE, PAY3),
603 I40E_PTT(24, IP, IPV4, NOF, NONE, NONE, NOF, UDP, PAY4),
605 I40E_PTT(26, IP, IPV4, NOF, NONE, NONE, NOF, TCP, PAY4),
606 I40E_PTT(27, IP, IPV4, NOF, NONE, NONE, NOF, SCTP, PAY4),
607 I40E_PTT(28, IP, IPV4, NOF, NONE, NONE, NOF, ICMP, PAY4),
610 I40E_PTT(29, IP, IPV4, NOF, IP_IP, IPV4, FRG, NONE, PAY3),
611 I40E_PTT(30, IP, IPV4, NOF, IP_IP, IPV4, NOF, NONE, PAY3),
612 I40E_PTT(31, IP, IPV4, NOF, IP_IP, IPV4, NOF, UDP, PAY4),
614 I40E_PTT(33, IP, IPV4, NOF, IP_IP, IPV4, NOF, TCP, PAY4),
[all …]
/Linux-v5.4/drivers/isdn/mISDN/
DKconfig30 tristate "ISDN over IP tunnel"
33 Enable support for ISDN over IP tunnel.
36 - dynamic IP exchange, if one or both peers have dynamic IPs
39 - direct tunneling of physical interface via IP
41 NOTE: This protocol is called 'Layer 1 over IP' and is not
/Linux-v5.4/drivers/infiniband/ulp/ipoib/
DKconfig3 tristate "IP-over-InfiniBand"
6 Support for the IP-over-InfiniBand protocol (IPoIB). This
7 transports IP packets over InfiniBand so you can use your IB
13 bool "IP-over-InfiniBand Connected Mode support"
28 bool "IP-over-InfiniBand debugging" if EXPERT
43 bool "IP-over-InfiniBand data path debugging"

12345678910>>...22