Home
last modified time | relevance | path

Searched refs:IP (Results 1 – 200 of 354) sorted by relevance

12

/linux-4.4.14/include/trace/events/
Drandom.h11 TP_PROTO(int bytes, unsigned long IP),
13 TP_ARGS(bytes, IP),
17 __field(unsigned long, IP )
22 __entry->IP = IP;
26 __entry->bytes, (void *)__entry->IP)
30 TP_PROTO(const char *pool_name, int bytes, unsigned long IP),
32 TP_ARGS(pool_name, bytes, IP),
37 __field(unsigned long, IP )
43 __entry->IP = IP;
47 __entry->pool_name, __entry->bytes, (void *)__entry->IP)
[all …]
Dbtrfs.h949 TP_PROTO(struct extent_state *state, gfp_t mask, unsigned long IP),
951 TP_ARGS(state, mask, IP),
962 __entry->ip = IP
971 TP_PROTO(struct extent_state *state, unsigned long IP),
973 TP_ARGS(state, IP),
982 __entry->ip = IP
/linux-4.4.14/drivers/net/ethernet/intel/i40evf/
Di40e_common.c613 I40E_PTT(22, IP, IPV4, FRG, NONE, NONE, NOF, NONE, PAY3),
614 I40E_PTT(23, IP, IPV4, NOF, NONE, NONE, NOF, NONE, PAY3),
615 I40E_PTT(24, IP, IPV4, NOF, NONE, NONE, NOF, UDP, PAY4),
617 I40E_PTT(26, IP, IPV4, NOF, NONE, NONE, NOF, TCP, PAY4),
618 I40E_PTT(27, IP, IPV4, NOF, NONE, NONE, NOF, SCTP, PAY4),
619 I40E_PTT(28, IP, IPV4, NOF, NONE, NONE, NOF, ICMP, PAY4),
622 I40E_PTT(29, IP, IPV4, NOF, IP_IP, IPV4, FRG, NONE, PAY3),
623 I40E_PTT(30, IP, IPV4, NOF, IP_IP, IPV4, NOF, NONE, PAY3),
624 I40E_PTT(31, IP, IPV4, NOF, IP_IP, IPV4, NOF, UDP, PAY4),
626 I40E_PTT(33, IP, IPV4, NOF, IP_IP, IPV4, NOF, TCP, PAY4),
[all …]
/linux-4.4.14/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 …]
Dipsec.txt5 1. IPcomp: Small IP packet won't get compressed at sender, and failed on
13 payload, the IP datagram MUST be sent in the original non-compressed
14 form. To clarify: If an IP datagram is sent non-compressed, no
17 the decompression processing cycles and avoiding incurring IP
21 Small IP datagrams are likely to expand as a result of compression.
23 where IP datagrams of size smaller than the threshold are sent in the
Dcdc_mbim.txt50 Establishing a MBIM IP session reequires at least these actions by the
55 - configure IP interface
163 mapped to MBIM IP session 0.
166 Multiplexed IP sessions (IPS)
168 MBIM allows multiplexing up to 256 IP sessions over a single USB data
169 channel. The cdc_mbim driver models such IP sessions as 802.1q VLAN
170 subdevices of the master wwanY device, mapping MBIM IP session Z to
177 VLAN links prior to establishing MBIM IP sessions where the SessionId
181 For example, adding a link for a MBIM IP session with SessionId 3:
186 IP session 3.
[all …]
Dgianfar.txt10 the 8548) has the ability to perform TCP, UDP, and IP checksums
13 the driver only supports checksumming for TCP/IP and UDP/IP
35 to align the IP header to a 16-byte boundary, when supported by
Dalias.txt2 IP-Aliasing:
5 IP-aliases are an obsolete way to manage multiple IP-addresses/masks
Dl2tp.txt3 more sessions over an IP tunnel. It is commonly used for VPNs
4 (L2TP/IPSec) and by ISPs to tunnel subscriber PPP sessions over an IP
14 L2TPv3 IP encapsulation.
29 change for L2TPv3 is that it can be carried directly over IP with no
50 provides L2TPv3 IP encapsulation (no UDP) and is implemented using a
70 such as "ip" and "ifconfig". If only IP frames are passed over the
71 tunnel, the interface can be given an IP addresses of itself and its
72 peer. If non-IP frames are to be passed over the tunnel, the interface
79 present in data frames - it is inferred from the IP connection on
213 and peer 192.168.1.2, using IP addresses 10.5.1.1 and 10.5.1.2 for the
[all …]
Darcnet.txt278 interface quite nicely with TCP/IP-based WfWg or Lan Manager
291 the SMC driver to work with the TCP/IP stuff included in the
324 one "required" by TCP/IP (576), there is a chance that some
326 TCP/IP layer can compensate in most cases, however, by
327 automatically fragmenting the TCP/IP packets to make them
363 ifconfig arc0 MY.IP.ADD.RESS
364 route add MY.IP.ADD.RESS arc0
369 ifconfig arc0 MY.IP.ADD.RESS
370 ifconfig arc0e MY.IP.ADD.RESS
371 route add MY.IP.ADD.RESS arc0e
[all …]
Dudplite.txt165 in turn, may trigger IP fragmentation. In this case, the generated
166 UDP-Lite packet is split into several IP packets, of which only the
177 Packet 1: 1024 payload + 8 byte header + 20 byte IP header = 1052 bytes
178 Packet 2: 512 payload + 8 byte header + 20 byte IP header = 540 bytes
200 header). According to the interface MTU, these are split into 4 IP
201 packets (280 byte IP payload + 20 byte IP header). The kernel module
203 the last packet before releasing the fragments to the IP module.
Dgeneric-hdlc.txt12 2. raw HDLC - either IP (IPv4) interface or Ethernet device emulation
47 any IP address to it) before using pvc devices.
64 * hdlc - sets raw HDLC (IP-only) mode
72 * cisco - sets Cisco HDLC mode (IP, IPv6 and IPX supported)
Dpktgen.txt131 pgset "dst 10.0.0.1" sets IP destination address
135 pgset "dst_max 10.0.0.254" Set the maximum destination IP.
136 pgset "src_min 10.0.0.1" Set the minimum (or only) source IP.
137 pgset "src_max 10.0.0.254" Set the maximum source IP.
155 are: IPSRC_RND # IP source is random (between min/max)
156 IPDST_RND # IP destination is random
232 -d : ($DEST_IP) destination IP
Dip-sysctl.txt15 forwarded) IP packets. Should be between 1 and 255 inclusive.
113 IP Fragmentation:
116 Maximum memory used to reassemble IP fragments. When
123 Maximum memory used to reassemble IP fragments before the kernel
128 Time in seconds to keep an IP fragment in memory.
133 common IP source address. Note that reordering of packets is
135 IP address while a particular fragment queue remains incomplete, it
139 ipfrag_max_dist (or more) fragments have arrived from a particular IP
140 address between additions to any IP fragment queue using that source
149 likelihood of incorrectly reassembling IP fragments that originate
[all …]
Dnetconsole.txt33 src-ip source IP to use (interface address)
36 tgt-ip IP address for logging agent
116 local_ip Source IP address to use (read-write)
117 remote_ip Remote agent's IP address (read-write)
210 only IP networks, UDP packets and ethernet devices are supported.
DREADME.sb100056 networking questions to get TCP/IP and PPP networking support.
116 IP addresses (like 204.71.200.67), be sure your /etc/resolv.conf file
117 has no syntax errors and has the right nameserver IP addresses in it.
131 numerical IP addresses. (This happens predominantly on Debian systems due
135 can share the same IP address as the ppp0 interface. Note that this
140 (in rc.local or some such) then any interfaces can share the same IP
176 denied packets on your broadcast interface (IP address xxx.yyy.zzz.255
D00-INDEX82 - serial IP load balancing
112 - IP dynamic address hack e.g. for auto-dialup links
114 - AppleTalk-IP Decapsulation and AppleTalk-IP Encapsulation
172 - IP policy-based routing
Dltpc.txt95 IP:
97 Yes, it is possible to do IP over LocalTalk. However, you can't just
101 Instead, you follow the same procedure as for doing IP in EtherTalk.
DPLIP.txt14 parallel ports to appear as a IP network interface.
19 PLIP is Parallel Line IP, that is, the transportation of IP packages
23 cable]. [The protocol used to pack IP packages, is a simple one
Dtuntap.txt26 IP packets (with tun) or ethernet frames (with tap). Which one is being used
106 Raw protocol(IP, IPv6, etc) frame.
215 TUN works with IP frames. TAP works with Ethernet frames.
217 This means that you have to read/write IP packets when you are using tun and
Dixgb.txt90 3. Assign an IP address to the interface by entering the following, where
96 is the IP address for another machine on the same subnet as the interface
162 A value of '1' indicates that the driver should enable IP checksum
258 be used by the IP stack to store incoming data.
392 one system on two IP networks in the same Ethernet broadcast domain
394 will respond to IP traffic for any IP address assigned to the system.
Dip_dynaddr.txt1 IP dynamic address hack-port v0.03
De100.txt155 one system on two IP networks in the same Ethernet broadcast domain
157 will respond to IP traffic for any IP address assigned to the system.
Dopenvswitch.txt76 e.g. source and destination addresses from Ethernet, IP, or TCP
183 assume that the flow contained IP packets. This is a bad assumption
184 (the flow only contains IP packets if one parses and skips over the
214 For example, consider a packet that contains an IP header that
215 indicates protocol 6 for TCP, but which is truncated just after the IP
Dsctp.txt6 SCTP (Stream Control Transmission Protocol) is a IP based, message oriented,
Dbatman-adv.txt5 does no longer operate on the IP basis. Unlike the batman daemon,
115 face. It needs an IP address which can be either statically con-
122 Note: In order to avoid problems remove all IP addresses previ-
Deql.txt1 EQL Driver: Serial IP Load Balancing HOWTO
6 that lets you load-balance IP serial links (SLIP or uncompressed PPP)
105 In rc.inet1, ifconfig the eql device to the IP address you usually use
470 it over twin SL/IP lines, just over null modems, but I was
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dtmio_mmc.txt14 "renesas,sdhi-sh7372" - SDHI IP on SH7372 SoC
15 "renesas,sdhi-sh73a0" - SDHI IP on SH73A0 SoC
16 "renesas,sdhi-r8a73a4" - SDHI IP on R8A73A4 SoC
17 "renesas,sdhi-r8a7740" - SDHI IP on R8A7740 SoC
18 "renesas,sdhi-r8a7778" - SDHI IP on R8A7778 SoC
19 "renesas,sdhi-r8a7779" - SDHI IP on R8A7779 SoC
20 "renesas,sdhi-r8a7790" - SDHI IP on R8A7790 SoC
21 "renesas,sdhi-r8a7791" - SDHI IP on R8A7791 SoC
22 "renesas,sdhi-r8a7792" - SDHI IP on R8A7792 SoC
23 "renesas,sdhi-r8a7793" - SDHI IP on R8A7793 SoC
[all …]
/linux-4.4.14/fs/jfs/
Djfs_btree.h63 #define BT_PAGE(IP, MP, TYPE, ROOT)\ argument
64 (BT_IS_ROOT(MP) ? (TYPE *)&JFS_IP(IP)->ROOT : (TYPE *)(MP)->data)
67 #define BT_GETPAGE(IP, BN, MP, TYPE, SIZE, P, RC, ROOT)\ argument
71 MP = (struct metapage *)&JFS_IP(IP)->bxflag;\
72 P = (TYPE *)&JFS_IP(IP)->ROOT;\
77 MP = read_metapage((IP), BN, SIZE, 1);\
89 #define BT_MARK_DIRTY(MP, IP)\ argument
92 mark_inode_dirty(IP);\
155 #define BT_GETSEARCH(IP, LEAF, BN, MP, TYPE, P, INDEX, ROOT)\ argument
162 P = (TYPE *)&JFS_IP(IP)->ROOT;\
Djfs_dtree.h162 #define PARENT(IP) \ argument
163 (le32_to_cpu(JFS_IP(IP)->i_dtroot.header.idotdot))
167 #define dtEmpty(IP) (JFS_IP(IP)->i_dtroot.header.nextindex == 0) argument
/linux-4.4.14/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 decribed 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-4.4.14/drivers/net/ethernet/intel/i40e/
Di40e_common.c612 I40E_PTT(22, IP, IPV4, FRG, NONE, NONE, NOF, NONE, PAY3),
613 I40E_PTT(23, IP, IPV4, NOF, NONE, NONE, NOF, NONE, PAY3),
614 I40E_PTT(24, IP, IPV4, NOF, NONE, NONE, NOF, UDP, PAY4),
616 I40E_PTT(26, IP, IPV4, NOF, NONE, NONE, NOF, TCP, PAY4),
617 I40E_PTT(27, IP, IPV4, NOF, NONE, NONE, NOF, SCTP, PAY4),
618 I40E_PTT(28, IP, IPV4, NOF, NONE, NONE, NOF, ICMP, PAY4),
621 I40E_PTT(29, IP, IPV4, NOF, IP_IP, IPV4, FRG, NONE, PAY3),
622 I40E_PTT(30, IP, IPV4, NOF, IP_IP, IPV4, NOF, NONE, PAY3),
623 I40E_PTT(31, IP, IPV4, NOF, IP_IP, IPV4, NOF, UDP, PAY4),
625 I40E_PTT(33, IP, IPV4, NOF, IP_IP, IPV4, NOF, TCP, PAY4),
[all …]
/linux-4.4.14/drivers/usb/usbip/
DKconfig2 tristate "USB/IP support"
5 This enables pushing USB packets over IP to allow remote
7 USB/IP core that is required by both drivers.
21 This enables the USB/IP virtual host controller driver,
31 This enables the USB/IP host driver, which is run on the
38 bool "Debug messages for USB/IP"
41 This enables the debug messages from the USB/IP drivers.
Dusbip_protocol.txt4 The USB/IP protocol follows a server/client architecture. The server exports the
9 client opens a TCP/IP connection towards the server, and sends an OP_REQ_DEVLIST
10 packet on top of the TCP/IP connection (so the actual OP_REQ_DEVLIST may be sent
13 TCP/IP connection is closed.
27 of them. First the client opens a TCP/IP connection towards the server and
29 import was successful the TCP/IP connection remains open and will be used
/linux-4.4.14/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-4.4.14/net/ipv4/
DKconfig2 # IP configuration
5 bool "IP: multicasting"
15 bool "IP: advanced router"
26 Note that your box can only act as a router if you enable IP
35 If you turn on IP forwarding, you should consider the rp_filter, which
39 so-called IP spoofing, however it can pose problems if you use
42 host which has several IP addresses on different interfaces. To turn
63 bool "IP: policy routing"
82 bool "IP: equal cost multipath"
94 bool "IP: verbose route monitoring"
[all …]
/linux-4.4.14/net/l2tp/
DKconfig19 L2TP is often used to tunnel PPP traffic over IP
20 tunnels. One IP tunnel may carry thousands of individual PPP
59 packet-oriented data network (e.g., over IP). L2TP, as
71 tristate "L2TP IP encapsulation for L2TPv3"
74 Support for L2TP-over-IP socket family.
77 L2TP frames, namely UDP and plain IP (without UDP). This
79 userspace L2TPv3 daemons may create L2TP/IP tunnel sockets
81 in IP packets, it used IP protocol number 115, so this port
98 across an IP network [RFC3931].
102 be used to assign an IP address to the local virtual
/linux-4.4.14/drivers/isdn/mISDN/
DKconfig29 tristate "ISDN over IP tunnel"
32 Enable support for ISDN over IP tunnel.
35 - dynamic IP exchange, if one or both peers have dynamic IPs
38 - direct tunneling of physical interface via IP
40 NOTE: This protocol is called 'Layer 1 over IP' and is not
/linux-4.4.14/drivers/infiniband/ulp/ipoib/
DKconfig2 tristate "IP-over-InfiniBand"
5 Support for the IP-over-InfiniBand protocol (IPoIB). This
6 transports IP packets over InfiniBand so you can use your IB
12 bool "IP-over-InfiniBand Connected Mode support"
27 bool "IP-over-InfiniBand debugging" if EXPERT
42 bool "IP-over-InfiniBand data path debugging"
/linux-4.4.14/Documentation/devicetree/bindings/gpu/
Dsamsung-rotator.txt5 (a) "samsung,exynos4210-rotator" for Rotator IP in Exynos4210
6 (b) "samsung,exynos4212-rotator" for Rotator IP in Exynos4212/4412
7 (c) "samsung,exynos5250-rotator" for Rotator IP in Exynos5250
9 - reg : Physical base address of the IP registers and length of memory
Dsamsung-g2d.txt5 (a) "samsung,s5pv210-g2d" for G2D IP present in S5PV210 & Exynos4210 SoC
6 (b) "samsung,exynos4212-g2d" for G2D IP present in Exynos4x12 SoCs
7 (c) "samsung,exynos5250-g2d" for G2D IP present in Exynos5250 SoC
9 - reg : Physical base address of the IP registers and length of memory
/linux-4.4.14/drivers/gpu/drm/sti/
DNOTES1 1. stiH display hardware IP
3 The STMicroelectronics stiH SoCs use a common chain of HW display IP blocks:
14 - The HDMI / DVO / HD Analog / SD analog IP builds the video signals
19 - The VTG (Video Timing Generators) build Vsync signals used by the other HW IP
20 Note that some stiH drivers support only a subset of thee HW IP.
39 These IP are mapped to the DRM objects as following:
/linux-4.4.14/drivers/net/appletalk/
DKconfig37 to do IP over it, or you have a LocalTalk card and wish to use it to
79 tristate "Appletalk-IP driver support"
82 This allows IP networking for users who only have AppleTalk
84 driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
90 If you say Y here, the AppleTalk-IP support will be compiled into
95 To compile the AppleTalk-IP support as a module, choose M here: the
102 bool "IP to Appletalk-IP Encapsulation support"
105 If you say Y here, the AppleTalk-IP code will be able to encapsulate
106 IP packets inside AppleTalk frames; this is useful if your Linux box
/linux-4.4.14/drivers/usb/dwc3/
DKconfig7 USB controller based on the DesignWare USB3 IP Core.
59 AM437x use this IP for USB2/3 functionality.
68 Recent Exynos5 SoCs ship with one DesignWare Core USB3 IP inside,
76 If you're using the DesignWare Core IP with a PCIe, please say
80 this IP.
95 STMicroelectronics SoCs with one DesignWare Core USB3 IP
104 Recent Qualcomm SoCs ship with one DesignWare Core USB3 IP inside,
/linux-4.4.14/Documentation/devicetree/bindings/rtc/
Drtc-omap.txt5 - "ti,da830-rtc" - for RTC IP used similar to that on DA8xx SoC family.
6 - "ti,am3352-rtc" - for RTC IP used similar to that on AM335x SoC family.
7 This RTC IP has special WAKE-EN Register to enable
11 - "ti,am4372-rtc" - for RTC IP used similar to that on AM437X SoC family.
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dst,sti-asoc-card.txt20 - reg: CPU DAI IP Base address and size entries, listed in same
36 - version: IP version integrated in SOC.
38 - dai-name: DAI name that describes the IP.
41 - clocks: CPU_DAI IP clock source, listed in the same order than the
44 - uniperiph-id: internal SOC IP instance ID.
46 - IP mode: IP working mode depending on associated codec.
47 "HDMI" connected to HDMI codec IP and IEC HDMI formats.
Domap-dmic.txt10 - ti,hwmods: Name of the hwmod associated with OMAP dmic IP
Dimx-audio-spdif.txt18 other IP block, such as an HDMI encoder or
Domap-mcbsp.txt13 McBSP IP have more interrupt lines:
/linux-4.4.14/Documentation/devicetree/bindings/display/
Dst,stih4xx.txt6 - reg: Physical base address of the IP registers and length of memory mapped region.
14 - reg: Physical base address of the IP registers and length of memory mapped region.
15 - clocks: from common clock binding: handle hardware IP needed clocks, the
32 - reg: Physical base address of the IP registers and length of memory mapped region.
33 - clocks: from common clock binding: handle hardware IP needed clocks, the
48 - reg: Physical base address of the IP registers and length of memory mapped region.
60 - reg: Physical base address of the IP registers and length of memory mapped region.
66 - clocks: from common clock binding: handle hardware IP needed clocks, the
76 - reg: Physical base address of the IP registers and length of memory mapped region.
79 - clocks: from common clock binding: handle hardware IP needed clocks, the
[all …]
/linux-4.4.14/Documentation/netlabel/
Dcipso_ipv4.txt9 The NetLabel CIPSO/IPv4 protocol engine is based on the IETF Commercial IP
17 The CIPSO/IPv4 protocol engine applies the CIPSO IP option to packets by
19 system through the socket to have the CIPSO IP option applied. The socket's
23 configured to use CIPSO for packet labeling then a CIPSO IP option will be
28 The CIPSO/IPv4 protocol engine validates every CIPSO IP option it finds at the
29 IP layer without any special handling required by the LSM. However, in order
Ddraft-ietf-cipso-ipsecurity-01.txt6 COMMERCIAL IP SECURITY OPTION (CIPSO 2.2)
13 IP Security Option (CIPSO). This draft reflects the version as approved by
37 IP datagrams to be labeled with security classifications. This option
110 including the type and length fields. With the current IP header length
146 information relevant to the data in the IP packet. Each tag begins with
154 be guaranteed if CIPSO is not the first IP option.
180 restrictions are based on the current IP limitation of 40 octets for all
181 IP options. If the IP header is later expanded, then the length and count
183 provided for IP options.
229 including the type and length fields. With the current IP header length
[all …]
/linux-4.4.14/drivers/usb/gadget/udc/bdc/
DKconfig2 tristate "Broadcom USB3.0 device controller IP driver(BDC)"
6 BDC is Broadcom's USB3.0 device controller IP. If your SOC has a BDC IP
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dmacb.txt5 Use "cdns,at91sam9260-macb" for Atmel at91sam9 SoCs or the 10/100Mbit IP
10 Use "atmel,sama5d2-gem" for the GEM IP (10/100) available on Atmel sama5d2 SoCs.
11 Use "atmel,sama5d3-gem" for the Gigabit IP available on Atmel sama5d3 SoCs.
12 Use "atmel,sama5d4-gem" for the GEM IP (10/100) available on Atmel sama5d4 SoCs.
Dfsl-fec.txt19 - fsl,num-tx-queues : The property is valid for enet-avb IP, which supports
22 - fsl,num-rx-queues : The property is valid for enet-avb IP, which supports
Dsocfpga-dwmac.txt16 altr,emac-splitter: Should be the phandle to the emac splitter soft IP node if
/linux-4.4.14/Documentation/devicetree/bindings/soc/mediatek/
Dpwrap.txt11 IP Pairing
16 are marked with "IP Pairing". These are optional on SoCs which do not support
17 IP Pairing
26 "pwrap-bridge": bridge base (IP Pairing)
30 "pwrap-bridge" (IP Pairing)
/linux-4.4.14/Documentation/infiniband/
Dipoib.txt1 IP OVER INFINIBAND
3 The ib_ipoib driver is an implementation of the IP over InfiniBand
43 transport and allows an MTU up to the maximal IP packet size of 64K,
44 which reduces the number of IP packets needed for handling large UDP
56 TCP/IP checksum and/or Large Send (LSO) offloading capability to the
100 Transmission of IP over InfiniBand (IPoIB) (RFC 4391)
102 IP over InfiniBand (IPoIB) Architecture (RFC 4392)
104 IP over InfiniBand: Connected Mode (RFC 4755)
/linux-4.4.14/net/tipc/
DKconfig28 IP-over-InfiniBand devices.
30 bool "IP/UDP media type support"
34 Saying Y here will enable support for running TIPC over IP/UDP
/linux-4.4.14/net/atm/
DKconfig22 tristate "Classical IP over ATM"
25 Classical IP over ATM for PVCs and SVCs, supporting InARP and
26 ATMARP. If you want to communication with other IP hosts on your ATM
68 bool "Per-VC IP filter kludge"
72 large number of IP-only vcc's. Do not enable this unless you are sure
/linux-4.4.14/Documentation/devicetree/bindings/
Dxilinx.txt1 d) Xilinx IP cores
3 The Xilinx EDK toolchain ships with a set of IP cores (devices) for use
10 Each IP-core has a set of parameters which the FPGA designer can use to
14 device drivers how the IP cores are configured, but it requires the kernel
20 properties of the device node. In general, device nodes for IP-cores
48 Typically, the compatible list will include the exact IP core version
49 followed by an older IP core version which implements the same
89 Some IP cores actually implement 2 or more logical devices. In
90 this case, the device should still describe the whole IP core with
92 ranges property can be used to translate from parent IP-core to the
[all …]
/linux-4.4.14/net/netfilter/ipvs/
DKconfig2 # IP Virtual Server configuration
5 tristate "IP virtual server support"
9 IP Virtual Server support will let you build a high-performance
13 single IP address and scheduling them to real servers.
38 bool "IP virtual server debugging"
41 debugging the IP virtual server code. You can change the debug
73 if IP VS was compiled built-in.
180 destination IP load balancing. It is usually used in cache cluster.
181 This algorithm usually directs packet destined for an IP address to
185 least-connection server to this IP address.
[all …]
/linux-4.4.14/Documentation/filesystems/nfs/
Dnfsroot.txt57 <server-ip> Specifies the IP address of the NFS server.
60 servers for IP autoconfiguration and NFS.
65 IP address.
84 This parameter tells the kernel how to configure IP addresses of devices
85 and also how to set up the IP routing table. It was originally called
86 `nfsaddrs', but now the boot-time IP configuration works independently of
101 <client-ip> IP address of the client.
105 <server-ip> IP address of the NFS server. If RARP is used to determine
116 <gw-ip> IP address of a gateway if the server is on a different subnet.
121 the netmask is derived from the client IP address assuming
[all …]
Dnfs-rdma.txt130 If you are using InfiniBand, be sure to enable IP-over-InfiniBand support.
163 is functioning as expected and standard NFS over TCP/IP and/or UDP/IP
202 test their functionality over standard Ethernet using TCP/IP or UDP/IP.
220 The IP address(es) is(are) the client's IPoIB address for an InfiniBand
/linux-4.4.14/drivers/net/ethernet/wiznet/
DKconfig26 PHY and hardware TCP/IP stack, but this driver is limited to
27 the MAC and PHY functions only, onchip TCP/IP is unused.
39 PHY and hardware TCP/IP stack, but this driver is limited to
40 the MAC and PHY functions only, onchip TCP/IP is unused.
/linux-4.4.14/drivers/media/platform/xilinx/
DKconfig2 tristate "Xilinx Video IP (EXPERIMENTAL)"
6 Driver for Xilinx Video IP Pipelines
/linux-4.4.14/tools/perf/arch/x86/tests/
Dregs_load.S11 #define IP 8 * 8 macro
43 movq %rax, IP(%rdi)
80 movl %eax, IP(%edi)
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-class-net-grcan9 Possible values: 0 or 1. See the GRCAN chapter of the GRLIB IP
21 Possible values: 0 or 1. See the GRCAN chapter of the GRLIB IP
32 values: 0 or 1. See the GRCAN chapter of the GRLIB IP core
Dsysfs-ibft13 Usually this contains the target's IP address, boot LUN,
23 Usually this contains the IP address, MAC, and gateway of the NIC.
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dexynos-jpeg-codec.txt9 - reg : address and length of the JPEG codec IP register set;
10 - interrupts : specifies the JPEG codec IP interrupt;
Dsamsung-fimc.txt68 fimc<n>, where <n> is an integer specifying the IP block instance.
79 - samsung,mainscaler-ext: a boolean property indicating whether the FIMC IP
81 - samsung,rotators: a bitmask specifying whether this IP has the input and
85 - samsung,cam-if: a bolean property indicating whether the IP block includes
87 - samsung,isp-wb: this property must be present if the IP block has the ISP
89 - samsung,lcd-wb: this property must be present if the IP block has the LCD
Ds5p-mfc.txt3 Multi Format Codec (MFC) is the IP present in Samsung SoCs which
16 - reg : Physical base address of the IP registers and length of memory
Dexynos-fimc-lite.txt16 fimc-lite<n>, where <n> is an integer specifying the IP block instance.
Dhix5hd2-ir.txt1 Device-Tree bindings for hix5hd2 ir IP
Dst,stih4xx.txt9 - clocks: from common clock binding: handle hardware IP needed clocks, the
Dst-rc.txt1 Device-Tree bindings for ST IRB IP
Dcoda.txt1 Chips&Media Coda multi-standard codec IP
/linux-4.4.14/Documentation/devicetree/bindings/mailbox/
Domap-mailbox.txt5 using a queued mailbox interrupt mechanism. The IP block is external to the
10 Each mailbox IP block has a certain number of h/w fifo queues and output
14 fixed for an instance and are dictated by the IP integration into the SoC
15 (excluding the SoCs that have a Interrupt Crossbar IP). Each interrupt line is
22 All the current OMAP SoCs except for the newest DRA7xx SoC has a single IP
30 A Mailbox device node is used to represent a Mailbox IP instance within a SoC.
51 - ti,mbox-num-fifos: Number of h/w fifo queues within the mailbox IP block
Dsti-mailbox.txt3 Each ST Mailbox IP currently consists of 4 instances of 32 channels. Messages
/linux-4.4.14/tools/perf/arch/arm/tests/
Dregs_load.S15 #define IP 0x60 macro
52 str ip, [r0, #IP]
/linux-4.4.14/Documentation/devicetree/bindings/input/
Dps2keyb-mouse-apbps2.txt3 The APBPS2 PS/2 core is available in the GRLIB VHDL IP core library.
15 For further information look in the documentation for the GLIB IP core library:
/linux-4.4.14/arch/x86/kernel/
Dvm86_32.c78 #define IP(regs) (*(unsigned short *)&((regs)->pt.ip)) macro
545 pushw(ssp, sp, IP(regs), cannot_handle); in do_int()
548 IP(regs) = segoffs & 0xffff; in do_int()
596 ip = IP(regs); in handle_vm86_fault()
627 IP(regs) = ip; in handle_vm86_fault()
641 IP(regs) = ip; in handle_vm86_fault()
654 IP(regs) = ip; in handle_vm86_fault()
682 IP(regs) = newip; in handle_vm86_fault()
695 IP(regs) = ip; in handle_vm86_fault()
707 IP(regs) = ip; in handle_vm86_fault()
/linux-4.4.14/arch/um/
DKconfig.net45 If you'd like to set up an IP network with the host and/or the
69 which can carry any Ethernet frame (and hence even non-IP packets),
70 the slip transport can only carry IP packets.
106 the host and/or other IP machines, say Y to the Ethertap or Slip
142 other IP machines.
144 To use this, your host kernel(s) must support IP Multicasting.
153 with other IP machines, make sure you select one of the other
181 known as SLiRP, a program that can re-socket IP packets back onto
182 the host on which it is run. Only IP packets are supported,
184 frames. In general, slirp allows the UML the same IP connectivity
/linux-4.4.14/Documentation/devicetree/bindings/display/exynos/
Dexynos_mixer.txt15 a) mixer: Gate of Mixer IP bus clock.
18 c) hdmi: Gate of HDMI IP bus clock, needed together with sclk_hdmi.
Dexynos_hdmi.txt17 a) hdmi: Gate of HDMI IP bus clock.
/linux-4.4.14/arch/blackfin/mach-bf533/boards/
DKconfig36 bool "IP04/IP08 IP-PBX"
39 Core support for IP04/IP04 open hardware IP-PBX.
/linux-4.4.14/Documentation/networking/caif/
DLinux-CAIF.txt22 * CAIF Socket Layer and GPRS IP Interface.
31 ! ! IP !! !Socket!!
100 - CFDGML CAIF Datagram layer. Handles CAIF Datagram layer (IP
156 CAIF Socket and IP interface
159 The IP interface and CAIF socket API are implemented on top of the
160 CAIF Core protocol. The IP Interface and CAIF socket have an instance of
/linux-4.4.14/tools/perf/arch/x86/util/
Dunwind-libdw.c27 dwarf_regs[8] = REG(IP); in libdw__arch_set_initial_registers()
46 dwarf_regs[16] = REG(IP); in libdw__arch_set_initial_registers()
Dperf_regs.c13 SMPL_REG(IP, PERF_REG_X86_IP),
/linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/ti/
Demif.txt4 TI SoCs. EMIF supports, based on the IP revision, one or more of
6 of the EMIF IP and memory parts attached to it.
10 is the IP revision of the specific EMIF instance.
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio-grgpio.txt3 The GRGPIO GPIO core is available in the GRLIB VHDL IP core library.
25 For further information look in the documentation for the GLIB IP core library:
Dgpio-dsp-keystone.txt4 the DSP GPIO controller IP. It provides 28 IRQ signals per each DSP core.
Dbrcm,kona-gpio.txt7 The Broadcom GPIO Controller IP can be configured prior to synthesis to
/linux-4.4.14/Documentation/devicetree/bindings/net/can/
Dgrcan.txt3 The GRCAN and CRHCAN CAN controllers are available in the GRLIB VHDL IP core
27 For further information look in the documentation for the GLIB IP core library:
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Dsnps,dw-apb-ictl.txt3 Synopsys DesignWare provides interrupt controller IP for APB known as
4 dw_apb_ictl. The IP is used as secondary interrupt controller in some SoCs with
Dti,keystone-irq.txt1 Keystone 2 IRQ controller IP
4 host using the IRQ controller IP. It provides 28 IRQ signals to ARM.
/linux-4.4.14/Documentation/
Dxillybus.txt51 again, pre-designed building blocks, IP cores, are often used. These are the
52 FPGA parallels of library functions. IP cores may implement certain
79 Xillybus is an IP core and a Linux driver. Together, they form a kit for
88 IP core. Rather, the IP core is configured and built based upon a
91 Xillybus presents independent data streams, which resemble pipes or TCP/IP
96 There may be more than a hundred of these streams on a single IP core, but
99 In order to ease the deployment of the Xillybus IP core, it contains a simple
103 driver is used to work out of the box with any Xillybus IP core.
116 names of these files depend on the IP core that is loaded in the FPGA (see
136 pieces of data sent across (like TCP/IP) by autoflushing.
[all …]
/linux-4.4.14/drivers/irqchip/
DKconfig159 a free irq and configures the IP. Thus the peripheral interrupts are
163 tristate "Keystone 2 IRQ controller IP"
166 Support for Texas Instruments Keystone 2 IRQ controller IP which
/linux-4.4.14/Documentation/isdn/
DREADME.syncppp39 'useifip' will get (if set to not 0.0.0.0) the IP address
41 (also: ipppd will try to negotiate pointopoint IP as remote IP)
DsyncPPP.FAQ13 Q10: I wanna use dynamic IP address assignment
27 in isdn4linux pushes all IP packets direct
152 Q10: I wanna use dynamic IP address assignment ... How
159 Now you must choose a dummy IP address for your
164 dynamic IP number and set a 'network route' for
176 Note: the IP address of the remote machine must be configured
178 If your side doesn't know the IP address after negotiation, it
/linux-4.4.14/Documentation/devicetree/bindings/display/imx/
Dhdmi.txt6 The HDMI Transmitter is a Synopsys DesignWare HDMI 1.4 TX controller IP
7 with accompanying PHY IP.
/linux-4.4.14/Documentation/devicetree/bindings/reset/
Dfsl,imx-src.txt24 Specifying reset lines connected to IP modules
28 IPU, and OpenVG IP modules on i.MX5 and i.MX6 ICs. Those device
Dsirf,rstc.txt21 Specifying reset lines connected to IP modules
/linux-4.4.14/drivers/usb/musb/
DKconfig12 controller based on the Mentor Graphics silicon IP. Then
17 Texas Instruments families using this IP include DaVinci
20 Analog Devices parts using this IP include Blackfin BF54x,
23 Allwinner SoCs using this IP include A10, A13, A20, ...
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Dpxa-usb.txt38 - interrupts: single interrupt generated by the UDC IP
39 - clocks: input clock of the UDC IP (see clock-bindings.txt)
Dgr-udc.txt4 IP core library.
33 For further information look in the documentation for the GLIB IP core library:
Dohci-st.txt16 - resets : phandle to the powerdown and reset controller for the USB IP
Dsamsung-hsotg.txt4 The Samsung HSOTG IP can be found on Samsung SoCs, from S3C6400 onwards.
Dehci-st.txt18 of the USB IP
Dqcom,dwc3.txt17 A child node must exist to represent the core DWC3 IP block. The name of
/linux-4.4.14/Documentation/devicetree/bindings/devfreq/event/
Dexynos-ppmu.txt5 each IP. PPMU provides the primitive values to get performance data. These
8 usages of each IP (DMC, CPU, RIGHTBUS, LEFTBUS, CAM interface, LCD, G3D, MFC).
11 derterming the current state of each IP.
/linux-4.4.14/Documentation/devicetree/bindings/power/
Dfsl,imx-gpc.txt39 Specifying power domain for IP modules
42 IP cores belonging to a power domain should contain a 'power-domains' property
/linux-4.4.14/Documentation/usb/
Dgadget-testing.txt82 Configure IP addresses of the device and the host. Then:
84 On the device: ping <host's IP>
85 On the host: ping <device's IP>
115 Configure IP addresses of the device and the host. Then:
117 On the device: ping <host's IP>
118 On the host: ping <device's IP>
148 Configure IP addresses of the device and the host. Then:
150 On the device: ping <host's IP>
151 On the host: ping <device's IP>
406 Configure IP addresses of the device and the host. Then:
[all …]
/linux-4.4.14/drivers/staging/clocking-wizard/
DKconfig9 Support for the Xilinx Clocking Wizard IP core clock generator.
Ddt-binding.txt1 Binding for Xilinx Clocking Wizard IP Core
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dsrio.txt8 Definition: Must include "fsl,srio" for IP blocks with IP Block
12 version in IP Block Revision Register and Y is Minor version. If this
Dsrio-rmu.txt15 The version X.Y should match the general SRIO controller's IP Block
46 The version X.Y should match the general SRIO controller's IP Block
76 The version X.Y should match the general SRIO controller's IP Block
106 The version X.Y should match the general SRIO controller's IP Block
Ddcsr.txt219 or Debug IP of the form "fsl,<soc>-dcsr-dpaa" in addition to the
247 or Debug IP of the form "fsl,<soc>-dcsr-ocn" in addition to the
307 or Debug IP of the form "fsl,<soc>-dcsr-nal" in addition to the
337 or Debug IP of the form "fsl,<soc>-dcsr-rcpm" in addition to the
/linux-4.4.14/drivers/ipack/devices/
DKconfig2 tristate "IndustryPack IP-OCTAL uart support"
/linux-4.4.14/arch/arm/boot/dts/
Danimeo_ip.dts2 * animeo_ip.dts - Device Tree file for Somfy Animeo IP Boards
13 model = "Somfy Animeo IP";
/linux-4.4.14/drivers/net/ethernet/calxeda/
DKconfig7 This is the driver for the XGMAC Ethernet IP block found on Calxeda
/linux-4.4.14/net/ipv4/netfilter/
DKconfig2 # IP netfilter configuration
5 menu "IP: Netfilter Configuration"
153 conflicting addresses. It works by modifying IP addresses
154 inside SNMP payloads to match IP-layer NAT mapping.
178 tristate "IP tables support (required for filtering/masq/NAT)"
291 only useful for dialup accounts with dynamic IP address (ie. your IP
349 an IP packet. This is particularly useful, if you need to work around
/linux-4.4.14/Documentation/arm/sti/
Dstih416-overview.txt8 for satellite, cable, terrestrial and IP-STB markets.
Dstih415-overview.txt8 for satellite, cable, terrestrial and IP-STB markets.
Dstih418-overview.txt9 and IP-STB markets.
Dstih407-overview.txt9 and IP-STB markets.
/linux-4.4.14/Documentation/devicetree/bindings/c6x/
Dsoc.txt15 - nodes for IP blocks within SoC
Dtimer64.txt15 - ti,dscr-dev-enable: Device ID used to enable timer IP through DSCR interface.
/linux-4.4.14/Documentation/devicetree/bindings/rng/
Dst,rng.txt6 reg : Base address and size of IP's register map.
Dqcom,prng.txt8 - clock-names : "core" clocks all registers, FIFO and circuits in PRNG IP block
Dst,stm32-rng.txt4 The STM32 hardware random number generator is a simple fixed purpose IP and
/linux-4.4.14/drivers/net/slip/
DKconfig50 TCP/IP headers (not on the data itself), but it has to be supported
72 Just occasionally you may need to run IP over hostile serial
77 end of the link as well. It's good enough, for example, to run IP
/linux-4.4.14/drivers/infiniband/hw/mlx5/
DKconfig8 IP-over-IB or SRP with these devices.
/linux-4.4.14/drivers/infiniband/hw/mlx4/
DKconfig10 IP-over-IB or SRP with these devices.
/linux-4.4.14/Documentation/devicetree/bindings/arm/freescale/
Dfsl,vf610-mscm-cpucfg.txt3 The MSCM IP contains multiple sub modules, this binding describes the first
Dfsl,vf610-mscm-ir.txt3 The MSCM IP contains multiple sub modules, this binding describes the second
/linux-4.4.14/net/bridge/
DKconfig25 turn your bridge into a bridging IP firewall.
26 iptables will then see the IP packets being bridged, so you need to
/linux-4.4.14/net/netfilter/ipset/
DKconfig2 tristate "IP set support"
6 This option adds IP set support to the kernel.
16 int "Maximum number of IP sets"
22 of IP sets for the kernel.
/linux-4.4.14/Documentation/filesystems/
Dceph.txt82 used instead of an IP address.
90 Specify the IP and/or port the client should bind to locally.
91 There is normally not much reason to do this. If the IP is not
92 specified, the client's IP address is determined by looking at the
Dncpfs.txt3 similar to the NFS used in the TCP/IP community.
Dafs.txt65 list of volume location server IP addresses:
163 IP addresses of the volume location servers for those cells. The cell to which
223 Here's what I use to test this. Some of the names and IP addresses are local
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dplda,xpressrich3-axi.txt9 - compatible: should contain "plda,xpressrich3-axi" to identify the IP used.
Darm,juno-r1-pcie.txt3 This PCIe host controller is based on PLDA XpressRICH3-AXI IP
Dfsl,imx6q-pcie.txt3 This PCIe host controller is based on the Synopsis Designware PCIe IP
Dsamsung,exynos5440-pcie.txt3 This PCIe host controller is based on the Synopsis Designware PCIe IP
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-emev2.txt7 - clocks : phandle to the IP core SCLK
/linux-4.4.14/drivers/gpu/drm/armada/
DKconfig15 performed by other IP found on the SoC. This driver provides
/linux-4.4.14/tools/perf/arch/arm/util/
Dunwind-libdw.c29 dwarf_regs[12] = REG(IP); in libdw__arch_set_initial_registers()
/linux-4.4.14/Documentation/devicetree/bindings/timer/
Dallwinner,sun5i-a13-hstimer.txt8 - interrupts : The interrupts of these timers (2 for the sun5i IP, 4 for the sun7i
Dsamsung,exynos4210-mct.txt39 Example 1: In this example, the IP contains two local timers, using separate
73 Example 3: In this example, the IP contains four local timers, but using
/linux-4.4.14/net/irda/irnet/
DKconfig10 IrNET is an alternate way to transfer TCP/IP traffic over IrDA. It
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dfsl,imx7d-pinctrl.txt57 advantages of LPSR power mode, is also possible that an IP to use pads from
58 any of the iomux controllers. For example the I2C1 IP can use SCL pad from
Dpinctrl-bindings.txt58 to be empty. This may be required when a common IP block is
61 the binding for that IP block requires certain pin states to
90 * For an IP block whose binding supports pin configuration,
/linux-4.4.14/arch/arm/plat-omap/
DKconfig24 bool "AVS(Adaptive Voltage Scaling) support for OMAP IP versions 1&2"
30 version 2 of the SmartReflex IP.
32 V2 is the update for the 45nm version of the IP used in OMAP3630
/linux-4.4.14/net/bridge/netfilter/
DKconfig83 MAC/IP address pairs can be matched, f.e. for anti-spoofing rules.
96 tristate "ebt: IP filter support"
98 This option adds the IP match, which allows basic IP header field
/linux-4.4.14/Documentation/devicetree/bindings/arm/omap/
Dl3-noc.txt3 This version is an implementation of the generic NoC IP
/linux-4.4.14/drivers/staging/rdma/ipath/
DKconfig9 as IP-over-InfiniBand as well as with userspace applications
/linux-4.4.14/drivers/firewire/
DKconfig48 tristate "IP networking over 1394"
51 This enables IPv4/IPv6 over IEEE 1394, providing IP connectivity
/linux-4.4.14/drivers/gpu/drm/rockchip/
DKconfig17 IP found on the SoC.
/linux-4.4.14/net/vmw_vsock/
DKconfig8 Virtual Socket Protocol is a socket protocol similar to TCP/IP
/linux-4.4.14/net/ipv6/
DKconfig10 Support for IP version 6 (IPv6).
82 Support for IP Payload Compression Protocol (IPComp) (RFC3173),
206 tristate "IPv6: IP-in-IPv6 tunnel (RFC2473)"
225 likes GRE much better than the other Linux tunneling driver ("IP
/linux-4.4.14/drivers/mcb/
DKconfig12 FPGA based devices. It is used to identify MCB based IP-Cores within
/linux-4.4.14/kernel/configs/
Dxen.config17 # You want TCP/IP and ELF binaries right?
/linux-4.4.14/net/mpls/
DKconfig31 tristate "MPLS: IP over MPLS tunnel support"
/linux-4.4.14/drivers/net/ethernet/samsung/
DKconfig26 This is the driver for the SXGBE 10G Ethernet IP block found on
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dkeystone-gate.txt3 Binding for Keystone gate control driver which uses PSC controller IP.
Dmarvell,berlin.txt9 (BG2, BG2CD, BG2Q) SoCs share the same IP for PLLs and clocks, with some
Dexynos5433-clock.txt13 which generates clocks for LLI (Low Latency Interface) IP.
32 which generates clocks for 3D Graphics Engine IP.
43 which generates clocks for MFC(Multi-Format Codec) IP.
45 which generates clocks for HEVC(High Efficiency Video Codec) decoder IP.
Dst,stm32-rcc.txt4 The RCC IP is both a reset and a clock controller. This documentation only
/linux-4.4.14/net/dns_resolver/
DKconfig13 being resolving a UNC hostname element to an IP address for CIFS or
/linux-4.4.14/Documentation/aoe/
Dtodo.txt9 Because ATA over Ethernet is not fragmented by the kernel's IP code,
/linux-4.4.14/drivers/usb/chipidea/
DKconfig7 controller based on ChipIdea silicon IP. Currently, only the
/linux-4.4.14/net/
DKconfig59 bool "TCP/IP networking"
66 system) use TCP/IP even if your machine is not connected to any
76 behavior of the TCP/IP code by writing to the (virtual) files in
131 globally valid IP addresses. This is called "masquerading": if one
183 tristate "Bridged IP/ARP packets filtering"
190 ARP resp. IP traffic. If you want a bridging firewall, you probably
/linux-4.4.14/drivers/staging/panel/
Dlcd-panel-cgram.txt18 printf "\e[LG60016051516141400;" => 6 = "IP"
/linux-4.4.14/Documentation/frv/
Dbooting.txt133 specify the IP address for the network device <iface>. <host> provide
143 This sets the IP address on the VDK motherboard RTL8029 ethernet chipset
149 kernel the IP address of the NFS server providing its root filesystem,
/linux-4.4.14/Documentation/cris/
DREADME124 NET4: Linux TCP/IP 1.0 for NET4.0
125 IP Protocols: ICMP, UDP, TCP
127 IP: routing cache hash table of 1024 buckets, 8Kbytes
/linux-4.4.14/net/8021q/
DKconfig11 firewalling, bridging, and of course IP traffic. You will need
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Datmel-hlcdc.txt16 The HLCDC IP exposes two subdevices:
/linux-4.4.14/Documentation/ia64/
DREADME37 include the library routines (IP checksum, etc.). Less
/linux-4.4.14/Documentation/acpi/apei/
Doutput_format.txt45 [IP: <integer>]
58 [restartable][, precise IP][, overflow][, corrected]
/linux-4.4.14/Documentation/bus-devices/
Dti-gpmc.txt13 IP details: http://www.ti.com/lit/pdf/spruh73 section 7.1
122 IP details (link above).
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt915 networking, or if you don't want to allocate an IP to your UML
960 tap0 interface an IP address.
964 Note that the IP address you assign to the host end of the tap device
965 must be different than the IP you assign to the eth device inside UML.
967 you can reuse the host's eth IP address for the host ends of the tap
1021 device IP address. It will provide the address fe:fd:nn:nn:nn:nn
1022 where nn.nn.nn.nn is the device IP address. This is nearly always
1028 may conflict with the UML IP address-based scheme
1030 o You aren't going to use the device for IP networking, so you don't
1031 assign the device an IP address
[all …]
/linux-4.4.14/crypto/
Ddes_generic.c524 #define IP(L, R, T) \ macro
815 IP(L, R, A); in des_encrypt()
838 IP(L, R, A); in des_decrypt()
904 IP(L, R, A); in des3_ede_encrypt()
935 IP(L, R, A); in des3_ede_decrypt()
/linux-4.4.14/drivers/net/ethernet/ibm/emac/
DKconfig36 will always reserve at least 2 bytes to make IP header
/linux-4.4.14/Documentation/devicetree/bindings/ata/
Dahci-st.txt16 - resets : The power-down, soft-reset and power-reset lines of SATA IP
/linux-4.4.14/samples/pktgen/
DREADME.rst21 -d : ($DEST_IP) destination IP
/linux-4.4.14/Documentation/i2c/busses/
Di2c-ocores13 IP core by Richard Herveille.
/linux-4.4.14/tools/usb/usbip/
DREADME9 - USB/IP device drivers
35 2. Compile & install USB/IP drivers.
/linux-4.4.14/tools/lguest/
Dlguest.txt83 IP address.
98 to obtain an IP address. The bridge needs to be configured first:
/linux-4.4.14/tools/perf/
Dbuiltin-script.c214 if (PRINT_FIELD(IP)) { in perf_evsel__check_attr()
225 if (PRINT_FIELD(SYM) && !PRINT_FIELD(IP) && !PRINT_FIELD(ADDR)) { in perf_evsel__check_attr()
236 if (PRINT_FIELD(DSO) && !PRINT_FIELD(IP) && !PRINT_FIELD(ADDR)) { in perf_evsel__check_attr()
242 if (PRINT_FIELD(SRCLINE) && !PRINT_FIELD(IP)) { in perf_evsel__check_attr()
281 if (PRINT_FIELD(IP)) in set_print_ip_opts()
400 else if (PRINT_FIELD(IP) && symbol_conf.use_callchain) in print_sample_start()
542 if (PRINT_FIELD(IP)) { in print_sample_bts()
624 if (PRINT_FIELD(IP)) { in process_event()
/linux-4.4.14/Documentation/memory-devices/
Dti-emif.txt40 - IP revision
/linux-4.4.14/Documentation/devicetree/bindings/display/rockchip/
Drockchip-vop.txt11 - interrupts: should contain a list of all VOP IP block interrupts in the
/linux-4.4.14/Documentation/devicetree/bindings/thermal/
Dtegra-soctherm.txt3 The SOCTHERM IP block contains thermal sensors, support for polled
/linux-4.4.14/net/decnet/
DKconfig10 to those which run over TCP/IP.
/linux-4.4.14/Documentation/devicetree/bindings/serial/
Dpl011.txt17 the clock named UARTCLK on the IP block, i.e. the clock
/linux-4.4.14/Documentation/devicetree/bindings/phy/
Dphy-bindings.txt29 That node describes an IP block (PHY provider) that implements 2 different PHYs.
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Darm-pl08x.txt8 - clocks: The clock running the IP core clock
/linux-4.4.14/tools/perf/Documentation/
Dperf-trace.txt137 fault); if no debug symbols available, perf trace will print raw IP;
148 for both IP and fault address in the form of dso@symbol+offset.
/linux-4.4.14/Documentation/block/
Ddata-integrity.txt61 system. Emulex, for instance, supports the TCP/IP checksum instead.
62 The IP checksum received from the OS is converted to the 16-bit CRC
67 The IP checksum is weaker than the CRC in terms of detecting bit
268 E.g. T10-DIF-TYPE1-IP or T13-EPP-0-CRC.

12