Searched full:network (Results 1 – 25 of 454) sorted by relevance
12345678910>>...19
| /Documentation/ABI/testing/ |
| D | sysfs-class-led-trigger-netdev | 6 Specifies the network device name to monitor.
26 Signal the link state of the named network device.
31 of the named network device.
40 Signal transmission of data on the named network device.
55 Signal reception of data on the named network device.
83 Signal the link speed state of 10Mbps of the named network device.
88 speed of 10MBps of the named network device.
91 Present only if the named network device supports 10Mbps link speed.
98 Signal the link speed state of 100Mbps of the named network device.
103 speed of 100Mbps of the named network device.
[all …]
|
| 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
59 Indicates the number of receive errors on this network device.
60 See the network driver for the exact meaning of this value.
[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 values 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.
59 Indicates the mux id associated to the qmimux network interface
|
| D | configfs-usb-gadget-phonet | 7 It contains the network interface name assigned during
8 network device registration.
|
| /Documentation/networking/device_drivers/ethernet/marvell/ |
| D | octeon_ep_vf.rst | 7 Network driver for Marvell's Octeon PCI EndPoint NIC VF.
18 * Network controller: Cavium, Inc. Device b203
19 * Network controller: Cavium, Inc. Device b403
20 * Network controller: Cavium, Inc. Device b103
21 * Network controller: Cavium, Inc. Device b903
22 * Network controller: Cavium, Inc. Device ba03
23 * Network controller: Cavium, Inc. Device bc03
24 * Network controller: Cavium, Inc. Device bd03
|
| D | octeon_ep.rst | 7 Network driver for Marvell's Octeon PCI EndPoint NIC.
25 * Network controller: Cavium, Inc. Device b100
26 * Network controller: Cavium, Inc. Device b200
27 * Network controller: Cavium, Inc. Device b400
28 * Network controller: Cavium, Inc. Device b900
29 * Network controller: Cavium, Inc. Device ba00
30 * Network controller: Cavium, Inc. Device bc00
31 * Network controller: Cavium, Inc. Device bd00
35 Network Interface control like changing mtu, link speed, link down/up are
|
| /Documentation/networking/device_drivers/ethernet/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 | samsung,exynos-nocp.yaml | 7 title: Samsung Exynos NoC (Network on Chip) Probe
14 The Samsung Exynos542x SoC has a NoC (Network on Chip) Probe for NoC bus.
16 that the Network on Chip (NoC) probes detects are transported over the
17 network infrastructure to observer units. You can configure probes to capture
18 packets with header or data on the data request response network, or as
|
| /Documentation/userspace-api/media/dvb/ |
| D | net.rst | 6 Digital TV Network API
10 of a transport stream to be mapped into a virtual network interface,
11 visible through the standard Linux network protocol stack.
19 In order to create the Linux virtual network interfaces, an application
23 virtual ``dvb?_?`` network interfaces, and will be controlled/routed via
|
| /Documentation/networking/ |
| D | sysfs-tagging.rst | 10 The problem. Network devices show up in sysfs and with the network
14 To avoid that problem and allow existing applications in network
18 By using the network namespace pointers as tags to separate out
21 the network devices.
|
| D | bridge.rst | 12 standard, is a device that connects two or more network segments and operates
56 bridge context, STP is crucial for network stability and availability.
76 network topology.
90 is a designated switch in a bridged network that serves as a reference point
100 in the network. The Bridge ID is used to compare the priorities of
102 3. Bridge Election: When the network starts, all bridges initially assume
112 network. This information is used by other bridges to calculate the
126 it to actively forward network traffic.
131 Blocking state to prevent network loops.
133 STP ensures network convergence by calculating the shortest path and disabling
[all …]
|
| D | gtp.rst | 19 and the interconnection between an external packet data network (such
24 such a tunnel between that external data network and the phone. The
32 At some network element inside the cellular operator infrastructure
40 and forwards it onto an external packet data network. This can be
41 public internet, but can also be any private IP network (or even
42 theoretically some non-IP network like X.25).
56 packet network in downlink towards the phone.
202 APN vs. Network Device
205 The GTP-U driver creates a Linux network device for each Gi/SGi
223 2. each private network manages its own addressing. In general this
[all …]
|
| D | tuntap.rst | 28 corresponding ioctl() to register a network device with the kernel. A network
30 the program closes the file descriptor, the network device and all
39 two network interfaces.
57 since CAP_NET_ADMIN is required for creating network devices or for
58 connecting to network devices which aren't owned by the user in question.
82 3.1 Network device allocation
86 "tun%d"), but (as far as I can see) this can be any valid network device name.
229 3. How does Virtual network device actually work ?
231 Virtual network device can be viewed as a simple Point-to-Point or
253 network interface. It does not provide a virtual network interface.
[all …]
|
| D | representors.rst | 5 Network Function Representors
16 Since the mid-2010s, network cards have started offering more complex
20 network connectivity of each function. The resulting designs are variously
23 Network function representors bring the standard Linux networking stack to
50 switchdev function, for each physical network port.
64 1. It is used to configure the network connection the representee sees, e.g.
76 bridge) to forward packets between representees and the rest of the network.
93 network port, which can simplify usage (the uplink netdev becomes in effect the
103 - PFs and VFs with other personalities, including network block devices (such
105 if) their network access is implemented through a virtual switch port. [#]_
[all …]
|
| D | bonding.rst | 28 multiple network interfaces into a single logical "bonded" interface.
63 4.2 Network Configuration
127 "make config"), then select "Bonding driver support" in the "Network
160 arp_ip_target parameters be specified, otherwise serious network
377 active slave. It is possible that some switch or network
387 Validation is useful in network configurations in which multiple
409 Filtering is useful in network configurations in which significant
498 the network must be updated via gratuitous ARP,
618 externally visible on only one port (network adapter)
901 it may be that your network device driver does not support
[all …]
|
| /Documentation/arch/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/networking/device_drivers/wwan/ |
| D | iosm.rst | 30 - configure network connection settings
31 - connect to network
32 - configure IP network interface
67 wwan0-X network device
70 traffic. Iproute network utility is used for creating "wwan0-X" network
81 The driver will automatically map the "wwan0-1" network device to MBIM IP
|
| /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/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/mm/ |
| D | page_frags.rst | 12 network stack and network device drivers to provide a backing region of
25 The network stack uses two separate caches per CPU to handle fragment
34 Many network device drivers use a similar methodology for allocating page
|
| /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
65 compatible = "intel,ixp4xx-network-processing-engine";
|
| /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 creates specialized network devices which are
38 stack. These specialized network interfaces are referred to as "user" 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
105 ``needed_tailroom`` properties are also used to request from the network stack,
120 From the perspective of the network stack, all switches within the same DSA
133 the network stack sees. This can be seen with Marvell switch trees, where the
162 mockup driver, which can be attached to any network interface. The goal is that
163 any network interface should be capable of transmitting the same packet in the
[all …]
|
| /Documentation/admin-guide/cifs/ |
| D | introduction.rst | 18 Apple systems also support SMB3 well, as do most Network Attached
19 Storage vendors, so this network filesystem client can mount to a
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/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
|
12345678910>>...19