Home
last modified time | relevance | path

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

12345678

/linux-3.4.99/include/trace/events/
Drandom.h11 TP_PROTO(const char *pool_name, int bytes, unsigned long IP),
13 TP_ARGS(pool_name, bytes, IP),
18 __field(unsigned long, IP )
24 __entry->IP = IP;
28 __entry->pool_name, __entry->bytes, (void *)__entry->IP)
32 TP_PROTO(const char *pool_name, int bytes, unsigned long IP),
34 TP_ARGS(pool_name, bytes, IP)
38 TP_PROTO(const char *pool_name, int bytes, unsigned long IP),
40 TP_ARGS(pool_name, bytes, IP)
45 int entropy_total, unsigned long IP),
[all …]
/linux-3.4.99/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 …]
Dalias.txt2 IP-Aliasing:
5 IP-aliases are an obsolete way to manage multiple IP-addresses/masks
Dgianfar.txt40 the 8548) has the ability to perform TCP, UDP, and IP checksums
43 the driver only supports checksumming for TCP/IP and UDP/IP
65 to align the IP header to a 16-byte boundary, when supported by
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 …]
/linux-3.4.99/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-3.4.99/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
110 you said Y to "AppleTalk-IP driver support" above and you say Y
[all …]
/linux-3.4.99/drivers/staging/usbip/
DKconfig2 tristate "USB/IP support (EXPERIMENTAL)"
6 This enables pushing USB packets over IP to allow remote
8 USB/IP core that is required by both drivers.
23 This enables the USB/IP virtual host controller driver,
34 This enables the USB/IP host driver, which is run on the
41 bool "Debug messages for USB/IP"
45 This enables the debug messages from the USB/IP drivers.
/linux-3.4.99/net/l2tp/
DKconfig17 L2TP is often used to tunnel PPP traffic over IP
18 tunnels. One IP tunnel may carry thousands of individual PPP
57 packet-oriented data network (e.g., over IP). L2TP, as
69 tristate "L2TP IP encapsulation for L2TPv3"
72 Support for L2TP-over-IP socket family.
75 L2TP frames, namely UDP and plain IP (without UDP). This
77 userspace L2TPv3 daemons may create L2TP/IP tunnel sockets
79 in IP packets, it used IP protocol number 115, so this port
96 across an IP network [RFC3931].
100 be used to assign an IP address to the local virtual
/linux-3.4.99/net/ipv4/
DKconfig2 # IP configuration
5 bool "IP: multicasting"
18 bool "IP: advanced router"
29 Note that your box can only act as a router if you enable IP
38 If you turn on IP forwarding, you should consider the rp_filter, which
42 so-called IP spoofing, however it can pose problems if you use
45 host which has several IP addresses on different interfaces. To turn
66 bool "IP: policy routing"
85 bool "IP: equal cost multipath"
97 bool "IP: verbose route monitoring"
[all …]
/linux-3.4.99/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-3.4.99/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-3.4.99/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-3.4.99/Documentation/infiniband/
Dipoib.txt1 IP OVER INFINIBAND
3 The ib_ipoib driver is an implementation of the IP over InfiniBand
40 transport and allows an MTU up to the maximal IP packet size of 64K,
41 which reduces the number of IP packets needed for handling large UDP
53 TCP/IP checksum and/or Large Send (LSO) offloading capability to the
97 Transmission of IP over InfiniBand (IPoIB) (RFC 4391)
99 IP over InfiniBand (IPoIB) Architecture (RFC 4392)
101 IP over InfiniBand: Connected Mode (RFC 4755)
/linux-3.4.99/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.
39 bool "IP virtual server debugging"
42 debugging the IP virtual server code. You can change the debug
74 if IP VS was compiled built-in.
160 destination IP load balancing. It is usually used in cache cluster.
161 This algorithm usually directs packet destined for an IP address to
165 least-connection server to this IP address.
[all …]
/linux-3.4.99/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-3.4.99/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-3.4.99/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.
83 This parameter tells the kernel how to configure IP addresses of devices
84 and also how to set up the IP routing table. It was originally called
85 `nfsaddrs', but now the boot-time IP configuration works independently of
100 <client-ip> IP address of the client.
104 <server-ip> IP address of the NFS server. If RARP is used to determine
115 <gw-ip> IP address of a gateway if the server is on a different subnet.
120 the netmask is derived from the client IP address assuming
[all …]
/linux-3.4.99/arch/x86/kernel/
Dvm86_32.c76 #define IP(regs) (*(unsigned short *)&((regs)->pt.ip)) macro
543 pushw(ssp, sp, IP(regs), cannot_handle); in do_int()
546 IP(regs) = segoffs & 0xffff; in do_int()
601 ip = IP(regs); in handle_vm86_fault()
632 IP(regs) = ip; in handle_vm86_fault()
646 IP(regs) = ip; in handle_vm86_fault()
659 IP(regs) = ip; in handle_vm86_fault()
685 IP(regs) = newip; in handle_vm86_fault()
698 IP(regs) = ip; in handle_vm86_fault()
710 IP(regs) = ip; in handle_vm86_fault()
/linux-3.4.99/sound/soc/s6000/
DKconfig13 tristate "SoC Audio support for Stretch 6105 IP Camera"
19 Stretch s6105 IP Camera Reference Design.
/linux-3.4.99/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-3.4.99/arch/blackfin/mach-bf533/boards/
DKconfig36 bool "IP04/IP08 IP-PBX"
39 Core support for IP04/IP04 open hardware IP-PBX.
/linux-3.4.99/Documentation/ABI/testing/
Dsysfs-ibft13 Usually this contains the target's IP address, boot LUN,
23 This can this can the IP address, MAC, and gateway of the NIC.

12345678