Searched full:network (Results 1 – 25 of 339) sorted by relevance
12345678910>>...14
| /Documentation/ABI/testing/ |
| D | sysfs-class-net-statistics | 6 Indicates the number of collisions seen by this network device.
15 network device.
22 Indicates the number of bytes received by this network device.
23 See the network driver for the exact meaning of when this
32 network device. This value might only be relevant for interfaces
41 by this network device. Note that the specific meaning might
49 Indicates the number of packets received by the network device
51 packet processing. See the network driver for the exact
60 network device. See the network driver for the exact
70 on the MAC layer protocol used. See the network driver for
[all …]
|
| D | sysfs-class-net-queues | 8 network device queue. Possible values depend on the number
17 processed by this particular network device receive queue.
25 network interface transmit queue.
42 network device transmit queue. Possible vaules depend on the
52 network device transmit queue. Possible values depend on the
53 number of available receive queue(s) in the network device.
62 of this particular network device transmit queue.
71 network device transmit queue.
79 on this network device transmit queue. This value is clamped
88 queued on this network device transmit queue. See
[all …]
|
| D | sysfs-class-net-qmi | 8 Set this to 'Y' to change the network device link
33 based network device, supported by recent Qualcomm based
36 The network device will be called qmimux.
38 Userspace is in charge of managing the qmux network device
50 created qmap mux based network device.
|
| D | sysfs-class-led-trigger-netdev | 6 Specifies the network device name to monitor.
21 Signal the link state of the named network device.
24 of the named network device.
32 Signal transmission of data on the named network device.
42 Signal reception of data on the named network device.
|
| D | configfs-usb-gadget-phonet | 7 It contains the network interface name assigned during
8 network device registration.
|
| /Documentation/networking/device_drivers/intel/ |
| D | e1000e.rst | 4 Linux Driver for Intel(R) Ethernet Network Connection
22 network drivers, refer to the Intel Support website:
34 There needs to be a <VAL#> for each network port in the system supported by
40 In this case, there are two network ports supported by e1000e in the system.
122 properly tuned for specific network traffic. Increasing this value adds extra
128 (stop transmitting) under certain network conditions. If this occurs a NETDEV
130 controller is automatically reset, restoring the network connection. To
142 RxIntDelay, may improve traffic throughput in specific network conditions.
151 properly tuned for specific network traffic. If the system is reporting
164 may improve traffic throughput in specific network conditions.
[all …]
|
| /Documentation/devicetree/bindings/devfreq/event/ |
| D | exynos-nocp.txt | 2 * Samsung Exynos NoC (Network on Chip) Probe device
4 The Samsung Exynos542x SoC has NoC (Network on Chip) Probe for NoC bus.
6 that the Network on Chip (NoC) probes detects are transported over
7 the network infrastructure to observer units. You can configure probes to
8 capture packets with header or data on the data request response network,
|
| /Documentation/networking/dsa/ |
| D | dsa.rst | 19 they configured/queried a switch port network device or a regular network
36 For each front-panel port, DSA will create specialized network devices which are
38 stack. These specialized network interfaces are referred to as "slave" network
54 Note that DSA does not currently create network interfaces for the "cpu" and
62 cannot really be used as proper network interfaces either, only the
83 Master network devices
86 Master network devices are regular, unmodified Linux network device drivers for
91 drivers. Such network devices are also often referred to as conduit network
105 Master network device (e.g.: e1000e):
134 - locate per-port network device
[all …]
|
| /Documentation/devicetree/bindings/firmware/ |
| D | intel,ixp4xx-network-processing-engine.yaml | 5 $id: "http://devicetree.org/schemas/firmware/intel,ixp4xx-network-processing-engine.yaml#"
8 title: Intel IXP4xx Network Processing Engine
14 On the IXP4xx SoCs, the Network Processing Engine (NPE) is a small
25 - const: intel,ixp4xx-network-processing-engine
42 compatible = "intel,ixp4xx-network-processing-engine";
|
| /Documentation/networking/ |
| D | gtp.txt | 13 and the interconnection between an external packet data network (such
18 such a tunnel between that external data network and the phone. The
26 At some network element inside the cellular operator infrastructure
34 and forwards it onto an external packet data network. This can be
35 public internet, but can also be any private IP network (or even
36 theoretically some non-IP network like X.25).
49 packet network in downlink towards the phone.
186 == APN vs. Network Device ==
188 The GTP-U driver creates a Linux network device for each Gi/SGi
206 > 2. each private network manages its own addressing. In general this
[all …]
|
| D | z8530book.rst | 11 a large number of cheap network interface cards. The kernel provides a
76 sense to make it match the network name.
103 Attaching Network Interfaces
106 If you wish to use the network interface facilities of the driver, then
107 you need to attach a network device to each channel that is present and
112 The network device used for each channel should be pointed to by the
113 netdevice field of each channel. The hdlc-> priv field of the network
119 private field of the network device. The network device fields of the
120 channels then point back to the network devices.
125 Before you register your network device you will also need to provide
[all …]
|
| D | tuntap.txt | 20 corresponding ioctl() to register a network device with the kernel. A network
22 the program closes the file descriptor, the network device and all
31 two network interfaces.
44 since CAP_NET_ADMIN is required for creating network devices or for
45 connecting to network devices which aren't owned by the user in question.
65 3.1 Network device allocation:
68 "tun%d"), but (as far as I can see) this can be any valid network device name.
201 3. How does Virtual network device actually work ?
202 Virtual network device can be viewed as a simple Point-to-Point or
222 network interface. It does not provide a virtual network interface.
[all …]
|
| D | netdevices.txt | 2 Network Devices, the Kernel, and You!
8 network devices.
12 Network device structures need to persist even after module is unloaded and
19 private data which gets freed when the network device is freed. If
20 separately allocated data is attached to the network device
25 Each network device has a Maximum Transfer Unit. The MTU does not
40 the MTU. A network device may use the MTU as mechanism to size receive
|
| D | ray_cs.txt | 7 802.11 compatible wireless network connectivity at 1 and 2 megabits/second.
51 class "network" module "misc/ray_cs"
61 To join an existing network with
62 different parameters, contact the network administrator for the
87 essid string ESS ID - network name to join
100 net_type integer 0 (default) = adhoc network,
119 network traffic using tcpdump or similar,
120 but no normal network use is allowed.
|
| D | bonding.txt | 22 multiple network interfaces into a single logical "bonded" interface.
58 4.2 Network Configuration
122 "make config"), then select "Bonding driver support" in the "Network
155 arp_ip_target parameters be specified, otherwise serious network
357 active slave. It is possible that some switch or network
367 Validation is useful in network configurations in which multiple
389 Filtering is useful in network configurations in which significant
455 the network must be updated via gratuitous ARP,
562 externally visible on only one port (network adapter)
833 it may be that your network device driver does not support
[all …]
|
| /Documentation/filesystems/ |
| D | sysfs-tagging.txt | 7 The problem. Network devices show up in sysfs and with the network
11 To avoid that problem and allow existing applications in network
15 By using the network namespace pointers as tags to separate out the
18 the network devices.
|
| /Documentation/arm/ |
| D | ixp4xx.rst | 2 Release Notes for Linux on Intel's IXP4xx Network Processor
10 Intel's IXP4xx network processor is a highly integrated SOC that
11 is targeted for network applications, though it has become popular
14 that support different network offload functions such as encryption,
21 http://developer.intel.com/design/network/products/npfamily/ixp4xx.htm
24 stripped of much of the network intelligence.
42 - Network interfaces (HSS, Utopia, NPEs, etc)
43 - Network offload functionality
48 http://developer.intel.com/design/network/products/npfamily/ixp425.htm
114 Gateworks Avila Network Platform
[all …]
|
| /Documentation/media/uapi/dvb/ |
| D | net.rst | 13 Digital TV Network API
17 of a transport stream to be mapped into a virtual network interface,
18 visible through the standard Linux network protocol stack.
26 In order to create the Linux virtual network interfaces, an application
30 virtual ``dvb?_?`` network interfaces, and will be controlled/routed via
|
| /Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 27 A typical RapidIO network is a combination of endpoints and switches.
52 A RapidIO device is any endpoint (other than mport) or switch in the network.
54 structure. Devices form one global device list and per-network device lists
71 2.4 Network
74 A RapidIO network is a combination of interconnected endpoint and switch devices.
75 Each RapidIO network known to the system is represented by corresponding rio_net
77 ports that form the same network. It also contains a pointer to the default
78 master port that is used to communicate with devices within the network.
84 intended to support specific RapidIO devices attached to the RapidIO network.
102 register at least one master port within the RapidIO network. To register mport
[all …]
|
| /Documentation/vm/ |
| D | page_frags.rst | 14 network stack and network device drivers to provide a backing region of
27 The network stack uses two separate caches per CPU to handle fragment
36 Many network device drivers use a similar methodology for allocating page
|
| /Documentation/netlabel/ |
| D | introduction.rst | 13 security attributes to outgoing network packets generated from user space
14 applications and read security attributes from incoming network packets. It
22 network packet's security attributes. If any translation between the network
|
| /Documentation/networking/device_drivers/dlink/ |
| D | dl2k.txt | 52 located at /etc/sysconfig/network-scripts or create it manually.
101 to a protocol stack in order to establish network connectivity. To load a
131 script that contains the necessary network information. A sample will be
141 to see the current network configuration.
156 1. Copy dl2k.o to the network modules directory, typically
167 3. Locate the network configuration scripts, normally the
168 /etc/sysconfig/network-scripts directory, and create a configuration
169 script named ifcfg-ethx that contains network information.
207 Virtual Local Area Network (VLAN) function is
226 has been a bottleneck for high speed network.
[all …]
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | net_prio.rst | 2 Network priority cgroup
5 The Network priority cgroup provides an interface to allow an administrator to
6 dynamically set the priority of network traffic generated by various
17 the priority of egress traffic on a given interface. Network priority groups can
|
| /Documentation/admin-guide/cifs/ |
| D | introduction.rst | 19 do most Network Attached Storage vendors, so this network
24 The intent of this module is to provide the most advanced network
32 the combination can provide a reasonable alternative to other network and
|
| /Documentation/networking/device_drivers/freescale/dpaa2/ |
| D | overview.rst | 16 DPAA2 is a hardware architecture designed for high-speeed network
26 network ports to create functional objects/devices such as network
58 | -network interface -DPNI |
78 in creating a network interfaces.
132 DPAA2 Objects for an Ethernet Network Interface
140 Ethernet network interface functionality. This approach provides
145 network interface configuration on a system with 2 CPUs.
185 DPNI (Datapath Network Interface)
186 Contains TX/RX queues, network interface configuration, and RX buffer pool
253 A network interface requires a 'buffer pool' (DPBP
[all …]
|
12345678910>>...14