Searched +full:rx +full:- +full:queues +full:- +full:to +full:- +full:use (Results 1 – 25 of 29) sorted by relevance
12
/Documentation/networking/device_drivers/ethernet/huawei/ |
D | hinic.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 The driver supports a range of link-speed devices (10GbE, 25GbE, 40GbE, etc.). 14 Some HiNIC devices support SR-IOV. This driver is used for Physical Function 17 HiNIC devices support MSI-X interrupt vector for each Tx/Rx queue and 21 TCP Transmit Segmentation Offload(TSO), Receive-Side Scaling(RSS) and 28 19e5:1822 - HiNIC PF 34 hinic_dev - Implement a Logical Network device that is independent from 37 hinic_hwdev - Implement the HW details of the device and include the components 55 Asynchronous Event Queues(AEQs) - The event queues for receiving messages from 58 Application Programmable Interface commands(API CMD) - Interface for sending [all …]
|
/Documentation/devicetree/bindings/net/ |
D | snps,dwmac.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Alexandre Torgue <alexandre.torgue@st.com> 11 - Giuseppe Cavallaro <peppe.cavallaro@st.com> 12 - Jose Abreu <joabreu@synopsys.com> 15 # will be able to report a warning when we have that compatible, since 16 # we will validate the node thanks to the select, but won't report it 23 - snps,dwmac 24 - snps,dwmac-3.50a [all …]
|
D | fsl-fec.txt | 4 - compatible : Should be "fsl,<soc>-fec" 5 - reg : Address and length of the register set for the device 6 - interrupts : Should contain fec interrupt 7 - phy-mode : See ethernet.txt file in the same directory 10 - phy-supply : regulator that powers the Ethernet PHY. 11 - phy-handle : phandle to the PHY device connected to this device. 12 - fixed-link : Assume a fixed link. See fixed-link.txt in the same directory. 13 Use instead of phy-handle. 14 - fsl,num-tx-queues : The property is valid for enet-avb IP, which supports 15 hw multi queues. Should specify the tx queue number, otherwise set tx queue [all …]
|
D | intel,dwmac-plat.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/net/intel,dwmac-plat.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Vineetha G. Jaya Kumaran <vineetha.g.jaya.kumaran@intel.com> 17 - intel,keembay-dwmac 19 - compatible 22 - $ref: "snps,dwmac.yaml#" 27 - items: 28 - enum: [all …]
|
D | keystone-netcp.txt | 6 switch sub-module to send and receive packets. NetCP also includes a packet 7 accelerator (PA) module to perform packet classification operations such as 13 includes a 3-port Ethernet switch sub-module capable of 10Gb/s and 1Gb/s rates 16 Keystone NetCP driver has a plug-in module architecture where each of the NetCP 17 sub-modules exist as a loadable kernel module which plug in to the netcp core. 18 These sub-modules are represented as "netcp-devices" in the dts bindings. It is 19 mandatory to have the ethernet switch sub-module for the ethernet interface to 20 be operational. Any other sub-module like the PA is optional. 24 ----------------------------- 26 ----------------------------- [all …]
|
/Documentation/networking/device_drivers/ethernet/freescale/ |
D | dpaa.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 - Madalin Bucur <madalin.bucur@nxp.com> 9 - Camelia Groza <camelia.groza@nxp.com> 13 - DPAA Ethernet Overview 14 - DPAA Ethernet Supported SoCs 15 - Configuring DPAA Ethernet in your kernel 16 - DPAA Ethernet Frame Processing 17 - DPAA Ethernet Features 18 - DPAA IRQ Affinity and Receive Side Scaling 19 - Debugging [all …]
|
/Documentation/networking/device_drivers/ethernet/intel/ |
D | i40e.rst | 1 .. SPDX-License-Identifier: GPL-2.0+ 8 Copyright(c) 1999-2018 Intel Corporation. 13 - Overview 14 - Identifying Your Adapter 15 - Intel(R) Ethernet Flow Director 16 - Additional Configurations 17 - Known Issues 18 - Support 25 For questions related to hardware requirements, refer to the documentation 26 supplied with your Intel adapter. All hardware requirements listed apply to use [all …]
|
D | iavf.rst | 1 .. SPDX-License-Identifier: GPL-2.0+ 8 Copyright(c) 2013-2018 Intel Corporation. 13 - Overview 14 - Identifying Your Adapter 15 - Additional Configurations 16 - Known Issues/Troubleshooting 17 - Support 28 CONFIG_PCI_MSI to be enabled. 30 The guest OS loading the iavf driver must support MSI-X interrupts. 44 For information on how to identify your adapter, and for the latest NVM/FW [all …]
|
D | ixgbe.rst | 1 .. SPDX-License-Identifier: GPL-2.0+ 8 Copyright(c) 1999-2018 Intel Corporation. 13 - Identifying Your Adapter 14 - Command Line Parameters 15 - Additional Configurations 16 - Known Issues 17 - Support 31 For information on how to identify your adapter, and for the latest Intel 32 network drivers, refer to the Intel Support website: 36 ---------------------------------- [all …]
|
/Documentation/devicetree/bindings/mailbox/ |
D | omap-mailbox.txt | 5 using a queued mailbox interrupt mechanism. The IP block is external to the 10 Each mailbox IP block/cluster has a certain number of h/w fifo queues and output 11 interrupt lines. An output interrupt line is routed to an interrupt controller 12 within a processor subsystem, and there can be more than one line going to a 16 programmable through a set of interrupt configuration registers, and have a rx 18 is achieved through the appropriate programming of the rx and tx interrupt 21 The number of h/w fifo queues and interrupt lines dictate the usable registers. 23 instance. DRA7xx has multiple instances with different number of h/w fifo queues 25 routed to different processor sub-systems on DRA7xx as they are routed through 29 all these clusters are multiplexed and routed to different processor subsystems [all …]
|
/Documentation/networking/ |
D | scaling.rst | 1 .. SPDX-License-Identifier: GPL-2.0 12 networking stack to increase parallelism and improve performance for 13 multi-processor systems. 17 - RSS: Receive Side Scaling 18 - RPS: Receive Packet Steering 19 - RFS: Receive Flow Steering 20 - Accelerated Receive Flow Steering 21 - XPS: Transmit Packet Steering 27 Contemporary NICs support multiple receive and transmit descriptor queues 28 (multi-queue). On reception, a NIC can send different packets to different [all …]
|
D | af_xdp.rst | 1 .. SPDX-License-Identifier: GPL-2.0 18 redirect ingress frames to other XDP enabled netdevs, using the 20 XDP programs to redirect frames to a memory buffer in a user-space 24 syscall. Associated with each XSK are two rings: the RX ring and the 25 TX ring. A socket can receive packets on the RX ring and it can send 28 to have at least one of these rings for each socket. An RX or TX 29 descriptor ring points to a data buffer in a memory area called a 30 UMEM. RX and TX can share the same UMEM so that a packet does not have 31 to be copied between RX and TX. Moreover, if a packet needs to be kept 32 for a while due to a possible retransmit, the descriptor that points [all …]
|
D | page_pool.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 per-page, but it can fallback on the regular page allocator APIs. 10 Basic use involves replacing alloc_pages() calls with the 11 page_pool_alloc_pages() call. Drivers should use page_pool_dev_alloc_pages() 14 API keeps track of inflight pages, in order to let API user know 15 when it is safe to free a page_pool object. Thus, API users 17 call page_pool_put_page() where appropriate in order to maintain correct 27 .. code-block:: none 29 +------------------+ 31 +------------------+ [all …]
|
D | net_dim.rst | 2 Net DIM - Generic Network Dynamic Interrupt Moderation 19 Dynamic Interrupt Moderation (DIM) (in networking) refers to changing the 20 interrupt moderation configuration of a channel in order to optimize packet 21 processing. The mechanism includes an algorithm which decides if and how to 25 to the previous sample and if required, it can decide to change some of the 30 the algorithm might decide not to change anything. The configuration fields are 32 number of wanted packets per event. The Net DIM algorithm ascribes importance to 42 #. Compares it to previous sample. 43 #. Makes a decision - suggests interrupt moderation configuration fields. 47 supplied by the driver registered to Net DIM. The previous data is the new data [all …]
|
/Documentation/networking/device_drivers/ethernet/ti/ |
D | cpsw.rst | 1 .. SPDX-License-Identifier: GPL-2.0 26 - TX queues must be rated starting from txq0 that has highest priority 27 - Traffic classes are used starting from 0, that has highest priority 28 - CBS shapers should be used with rated queues 29 - The bandwidth for CBS shapers has to be set a little bit more then 30 potential incoming rate, thus, rate of all incoming tx queues has 31 to be a little less 32 - Real rates can differ, due to discreetness 33 - Map skb-priority to txq is not enough, also skb-priority to l2 prio 34 map has to be created with ip or vconfig tool [all …]
|
/Documentation/networking/device_drivers/ethernet/stmicro/ |
D | stmmac.rst | 1 .. SPDX-License-Identifier: GPL-2.0+ 13 - In This Release 14 - Feature List 15 - Kernel Configuration 16 - Command Line Parameters 17 - Driver Information and Notes 18 - Debug Information 19 - Support 33 (and older) and DesignWare(R) Cores Ethernet Quality-of-Service version 4.0 35 DesignWare(R) Cores XGMAC - 10G Ethernet MAC and DesignWare(R) Cores [all …]
|
/Documentation/devicetree/bindings/soc/ti/ |
D | keystone-navigator-dma.txt | 6 the actual data movements across clients using destination queues. Every 13 ------------------ 15 ------------------ 17 |-> DMA instance #0 19 |-> DMA instance #1 23 |-> DMA instance #n 27 - compatible: Should be "ti,keystone-navigator-dma" 28 - clocks: phandle to dma instances clocks. The clock handles can be as 31 - ti,navigator-cloud-address: Should contain base address for the multi-core 33 configuration.. Navigator cloud global address needs to be programmed [all …]
|
/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
D | overview.rst | 16 DPAA2 is a hardware architecture designed for high-speeed network 23 DPAA2 hardware resources. The MC provides an object-based abstraction for 24 software drivers to use the DPAA2 hardware. 25 The MC uses DPAA2 hardware resources such as queues, buffer pools, and 26 network ports to create functional objects/devices such as network 28 The MC provides memory-mapped I/O command interfaces (MC portals) 29 which DPAA2 software drivers use to operate on DPAA2 objects. 34 +--------------------------------------+ 38 +-----------------------------|--------+ 41 | config,use,destroy) [all …]
|
/Documentation/networking/device_drivers/ethernet/microsoft/ |
D | netvsc.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 Hyper-V network driver 17 ---------------- 19 Hyper-V host version does. Windows Server 2016 and Azure 24 -------------------- 25 Hyper-V supports receive side scaling. For TCP & UDP, packets can 26 be distributed among available queues based on IP address and port 39 To include UDP port numbers in hashing:: 41 ethtool -N eth0 rx-flow-hash udp4 sdfn 43 To exclude UDP port numbers in hashing:: [all …]
|
/Documentation/networking/device_drivers/ethernet/aquantia/ |
D | atlantic.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 For the aQuantia Multi-Gigabit PCI Express Family of Ethernet Adapters 12 - Identifying Your Adapter 13 - Configuration 14 - Supported ethtool options 15 - Command Line Parameters 16 - Config file parameters 17 - Support 18 - License 23 The driver in this release is compatible with AQC-100, AQC-107, AQC-108 [all …]
|
/Documentation/networking/device_drivers/ethernet/amazon/ |
D | ena.rst | 1 .. SPDX-License-Identifier: GPL-2.0 10 ENA is a networking interface designed to make good use of modern CPU 17 The driver supports a range of ENA devices, is link-speed independent 21 Some ENA devices support SR-IOV. This driver is used for both the 22 SR-IOV Physical Function (PF) and Virtual Function (VF) devices. 25 processing by providing multiple Tx/Rx queue pairs (the maximum number 26 is advertised by the device via the Admin Queue), a dedicated MSI-X 27 interrupt vector per Tx/Rx queue pair, adaptive interrupt moderation, 32 Receive-side scaling (RSS) is supported for multi-core scaling. 36 to recover in a manner transparent to the application, as well as [all …]
|
/Documentation/userspace-api/media/cec/ |
D | cec-ioc-receive.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 14 CEC_RECEIVE, CEC_TRANSMIT - Receive or transmit a CEC message 34 Pointer to struct cec_msg. 39 To receive a CEC message the application has to fill in the 40 ``timeout`` field of struct :c:type:`cec_msg` and pass it to 42 If the file descriptor is in non-blocking mode and there are no received 43 messages pending, then it will return -1 and set errno to the ``EAGAIN`` 45 is non-zero and no message arrived within ``timeout`` milliseconds, then 46 it will return -1 and set errno to the ``ETIMEDOUT`` error code. 52 2. the result of an earlier non-blocking transmit (the ``sequence`` field will [all …]
|
/Documentation/driver-api/nfc/ |
D | nfc-hci.rst | 5 - Author: Eric Lapuyade, Samuel Ortiz 6 - Contact: eric.lapuyade@intel.com, samuel.ortiz@intel.com 9 ------- 12 enables easy writing of HCI-based NFC drivers. The HCI layer runs as an NFC Core 14 to HCI commands and events. 17 --- 20 routed through netlink sockets to NFC Core and then to HCI. From this point, 21 they are translated in a sequence of HCI commands sent to the HCI layer in the 24 from HCI Rx context). 26 and a translation will be forwarded to NFC Core as needed. There are hooks to [all …]
|
/Documentation/hid/ |
D | intel-ish-hid.rst | 5 A sensor hub enables the ability to offload sensor polling and algorithm 6 processing to a dedicated low power co-processor. This allows the core 7 processor to go into low power modes more often, resulting in the increased 10 There are many vendors providing external sensor hubs confirming to HID 17 These ISH also comply to HID sensor specification, but the difference is the 19 mainly use HID over i2C or USB. But ISH doesn't use either i2c or USB. 27 ----------------- ---------------------- 28 | USB HID | --> | ISH HID | 29 ----------------- ---------------------- 30 ----------------- ---------------------- [all …]
|
/Documentation/networking/dsa/ |
D | sja1105.rst | 10 - SJA1105E: First generation, no TTEthernet 11 - SJA1105T: First generation, TTEthernet 12 - SJA1105P: Second generation, no TTEthernet, no SGMII 13 - SJA1105Q: Second generation, TTEthernet, no SGMII 14 - SJA1105R: Second generation, no TTEthernet, SGMII 15 - SJA1105S: Second generation, TTEthernet, SGMII 17 These are SPI-managed automotive switches, with all ports being gigabit 21 set-and-forget use, with minimal dynamic interaction at runtime. They 22 require a static configuration to be composed by software and packed 56 Also the configuration is write-only (software cannot read it back from the [all …]
|
12