Searched +full:max +full:- +full:virtual +full:- +full:functions (Results 1 – 25 of 27) sorted by relevance
12
| /Documentation/devicetree/bindings/pci/ |
| D | pci-ep.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/pci-ep.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
13 - Kishon Vijay Abraham I <kishon@kernel.org>
14 - Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
18 pattern: "^pcie-ep@"
20 max-functions:
21 description: Maximum number of functions that can be configured
27 max-virtual-functions:
[all …]
|
| D | snps,dw-pcie-ep.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-ep.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
16 # Please create a separate DT-schema for your DWC PCIe Endpoint controller
17 # and make sure it's assigned with the vendor-specific compatible string.
21 const: snps,dw-pcie-ep
23 - compatible
[all …]
|
| D | snps,dw-pcie.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
16 # Please create a separate DT-schema for your DWC PCIe Root Port controller
17 # and make sure it's assigned with the vendor-specific compatible string.
21 const: snps,dw-pcie
23 - compatible
[all …]
|
| /Documentation/misc-devices/ |
| D | mrvl_cn10k_dpi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 DPI hardware comprises a physical function (PF), its virtual functions,
15 requests from its VF functions and provisions DMA engine resources to
16 it's VF functions.
21 /dev/mrvl-cn10k-dpi node to set DMA engine and PEM (PCIe interface) port
37 ioctl that sets max payload size & max read request size parameters of
42 ioctl that sets DMA engine's fifo sizes & max outstanding load request
49 vfio-pci driver. Below is a sample dpi dma application to demonstrate on
52 https://github.com/MarvellEmbeddedProcessors/dpi-sample-app
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | iavf.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
4 Linux Base Driver for Intel(R) Ethernet Adaptive Virtual Function
7 Intel Ethernet Adaptive Virtual Function Linux driver.
8 Copyright(c) 2013-2018 Intel Corporation.
13 - Overview
14 - Identifying Your Adapter
15 - Additional Configurations
16 - Known Issues/Troubleshooting
17 - Support
25 The iavf driver supports the below mentioned virtual function devices and
[all …]
|
| 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
47 ----------------------
49 …intel.com/content/dam/www/public/us/en/documents/release-notes/xl710-ethernet-controller-feature-m…
[all …]
|
| D | ice.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 2018-2021 Intel Corporation.
13 - Overview
14 - Identifying Your Adapter
15 - Important Notes
16 - Additional Features & Configurations
17 - Performance Optimization
20 The associated Virtual Function (VF) driver for this driver is iavf.
28 This driver supports XDP (Express Data Path) and AF_XDP zero-copy. Note that
43 -------------------------------------------
[all …]
|
| /Documentation/hwmon/ |
| D | pmbus-core.rst | 9 power-management protocol with a fully defined command language that facilitates
11 protocol is implemented over the industry-standard SMBus serial interface and
12 enables programming, control, and real-time monitoring of compliant power
18 promoted by the PMBus Implementers Forum (PMBus-IF), comprising 30+ adopters
22 commands, and manufacturers can add as many non-standard commands as they like.
23 Also, different PMBUs devices act differently if non-supported commands are
43 PMBus device capabilities auto-detection
46 For generic PMBus devices, code in pmbus.c attempts to auto-detect all supported
47 PMBus commands. Auto-detection is somewhat limited, since there are simply too
50 pages (see the PMBus specification for details on multi-page PMBus devices).
[all …]
|
| /Documentation/core-api/ |
| D | rbtree.rst | 2 Red-black Trees (rbtree) in Linux
9 What are red-black trees, and what are they for?
10 ------------------------------------------------
12 Red-black trees are a type of self-balancing binary search tree, used for
19 Red-black trees are similar to AVL trees, but provide faster real-time bounded
26 There are a number of red-black trees in use in the kernel.
29 The high-resolution timer code uses an rbtree to organize outstanding
31 red-black tree. Virtual memory areas (VMAs) are tracked with red-black
38 Linux Weekly News article on red-black trees
41 Wikipedia entry on red-black trees
[all …]
|
| /Documentation/arch/arm/omap/ |
| D | dss.rst | 7 TV-out and multiple display support, but there are lots of small improvements
10 The DSS2 driver (omapdss module) is in arch/arm/plat-omap/dss/, and the FB,
15 --------
19 - MIPI DPI (parallel) output
20 - MIPI DSI output in command mode
21 - MIPI DBI (RFBI) output
22 - SDI output
23 - TV output
24 - All pieces can be compiled as a module or inside kernel
25 - Use DISPC to update any of the outputs
[all …]
|
| /Documentation/usb/ |
| D | gadget-testing.rst | 5 This file summarizes information on basic testing of USB functions
38 Function-specific configfs interface
39 ------------------------------------
46 The attribute is read-only.
52 ------------------------
77 Function-specific configfs interface
78 ------------------------------------
93 and after creating the functions/ecm.<instance name> they contain default
100 ------------------------
117 Function-specific configfs interface
[all …]
|
| /Documentation/userspace-api/accelerators/ |
| D | ocxl.rst | 6 at being low-latency and high-bandwidth. The specification is
10 the host memory coherently, using virtual addresses. An OpenCAPI
14 OpenCAPI is known in linux as 'ocxl', as the open, processor-agnostic
20 High-level view
29 +-----------+ +-------------+
33 | | +--------+ | Unit | +--------+
34 | |--| Memory | | (AFU) |--| Memory |
35 | | +--------+ | | +--------+
36 +-----------+ +-------------+
38 +-----------+ +-------------+
[all …]
|
| /Documentation/trace/ |
| D | kprobes.rst | 29 collect debugging and performance information non-disruptively. You
41 In the typical case, Kprobes-based instrumentation is packaged as
48 There are also ``register_/unregister_*probes()`` functions for batch
49 registration/unregistration of a group of ``*probes``. These functions
56 Kprobes -- e.g., the difference between a pre_handler and
62 -----------------------
74 Next, Kprobes single-steps its copy of the probed instruction.
75 (It would be simpler to single-step the actual instruction in place,
80 After the instruction is single-stepped, Kprobes executes the
85 -----------------------
[all …]
|
| /Documentation/networking/devlink/ |
| D | ice.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 .. list-table:: Generic parameters implemented
16 * - Name
17 - Mode
18 - Notes
19 * - ``enable_roce``
20 - runtime
21 - mutually exclusive with ``enable_iwarp``
22 * - ``enable_iwarp``
23 - runtime
[all …]
|
| /Documentation/ABI/testing/ |
| D | debugfs-driver-qat_telemetry | 4 Contact: qat-linux@intel.com
16 * 1-4: telemetry is enabled and running
40 Contact: qat-linux@intel.com
55 max_gp_lat max get to put latency [ns] (only takes
98 <counter_name> <current> <min> <max> <avg>
108 Contact: qat-linux@intel.com
114 * 0 to ``<num_rps - 1>``:
117 See Documentation/ABI/testing/sysfs-driver-qat.
160 <counter_name> <current> <min> <max> <avg>
165 If Virtual Functions (VF) are used, the ring pair number can
[all …]
|
| /Documentation/ |
| D | memory-barriers.txt | 19 documentation at tools/memory-model/. Nevertheless, even this memory
37 Note also that it is possible that a barrier may be a no-op for an
48 - Device operations.
49 - Guarantees.
53 - Varieties of memory barrier.
54 - What may not be assumed about memory barriers?
55 - Address-dependency barriers (historical).
56 - Control dependencies.
57 - SMP barrier pairing.
58 - Examples of memory barrier sequences.
[all …]
|
| /Documentation/scsi/ |
| D | ChangeLog.lpfc | 2 * Please read the associated RELEASE-NOTES file !!!
8 * Fixed build warning for 2.6.12-rc2 kernels: mempool_alloc now
19 * Removed FC_TRANSPORT_PATCHESxxx defines. They're in 2.6.12-rc1.
26 * Added PCI ID for LP10000-S.
31 * Zero-out response sense length in lpfc_scsi_prep_cmnd to prevent
33 - was causing spurious 0710 messages.
55 - stop using volatile. if you need special ordering use memory
57 - switch lpfc_sli_pcimem_bcopy to take void * arguments.
58 - remove typecast for constants - a U postfix marks them
60 - add a MAILBOX_CMD_SIZE macro, as most users of
[all …]
|
| /Documentation/networking/device_drivers/ethernet/netronome/ |
| D | nfp.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
14 - `Overview`_
15 - `Acquiring Firmware`_
16 - `Devlink Info`_
17 - `Configure Device`_
18 - `Statistics`_
25 are also incorporated in the companies' family of Agilio SmartNICs. The SR-IOV
26 physical and virtual functions for these devices are supported by the driver.
35 Firmware files on the host filesystem contain card type (`AMDA-*` string), media
40 `linux-firmware.git` repository.
[all …]
|
| /Documentation/sound/kernel-api/ |
| D | writing-an-alsa-driver.rst | 11 Architecture) <http://www.alsa-project.org/>`__ driver. The document
19 low-level driver implementation details. It only describes the standard
26 -------
56 --------------
60 sub-directories contain different modules and are dependent upon the
74 This directory and its sub-directories are for the ALSA sequencer. This
76 as snd-seq-midi, snd-seq-virmidi, etc. They are compiled only when
85 -----------------
88 to be exported to user-space, or included by several files in different
94 -----------------
[all …]
|
| /Documentation/networking/ |
| D | tls-offload.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
13 For details regarding the user-facing interface refer to the TLS
18 * Software crypto mode (``TLS_SW``) - CPU handles the cryptography.
24 * Packet-based NIC offload mode (``TLS_HW``) - the NIC handles crypto
28 (``ethtool`` flags ``tls-hw-tx-offload`` and ``tls-hw-rx-offload``).
29 * Full TCP NIC offload mode (``TLS_HW_RECORD``) - mode of operation where
33 abilities or QoS and packet scheduling (``ethtool`` flag ``tls-hw-record``).
36 offload opt-in or opt-out on per-connection basis is not currently supported.
39 --
52 --
[all …]
|
| D | ethtool-netlink.rst | 27 wake-on-lan password) omitted.
37 number 1 but any non-zero value should be understood as "true" by recipient.
44 Attributes that need to be filled-in by device drivers and that are dumped to
98 representing bit values and mask of affected bits) and bit-by-bit (list of
101 Verbose (bit-by-bit) bitsets allow sending symbolic names for bits together
126 rounded up to a multiple of 32 bits. They consist of 32-bit words in host byte
141 Bit-by-bit form: nested (bitset) attribute contents:
143 +------------------------------------+--------+-----------------------------+
145 +------------------------------------+--------+-----------------------------+
147 +------------------------------------+--------+-----------------------------+
[all …]
|
| D | af_xdp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 XDP programs to redirect frames to a memory buffer in a user-space
64 single-consumer / single-producer (for performance reasons), the new
72 user-space application can place an XSK at an arbitrary place in this
99 http://vger.kernel.org/lpc_net2018_talks/lpc18_paper_af_xdp_perf-v2.pdf. Do
106 ----
108 UMEM is a region of virtual contiguous memory, divided into
109 equal-sized frames. An UMEM is associated to a netdev and a specific
121 The UMEM has two single-producer/single-consumer rings that are used
123 user-space application.
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-infiniband | 2 -------------------------------------------------
9 Contact: linux-rdma@vger.kernel.org
24 Contact: linux-rdma@vger.kernel.org
34 Contact: linux-rdma@vger.kernel.org
39 What: /sys/class/infiniband/<device>/ports/<port-num>/lid
40 What: /sys/class/infiniband/<device>/ports/<port-num>/rate
41 What: /sys/class/infiniband/<device>/ports/<port-num>/lid_mask_count
42 What: /sys/class/infiniband/<device>/ports/<port-num>/sm_sl
43 What: /sys/class/infiniband/<device>/ports/<port-num>/sm_lid
44 What: /sys/class/infiniband/<device>/ports/<port-num>/state
[all …]
|
| /Documentation/virt/kvm/ |
| D | api.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 The Definitive KVM (Kernel-based Virtual Machine) API Documentation
11 of a virtual machine. The ioctls belong to the following classes:
13 - System ioctls: These query and set global attributes which affect the
15 virtual machines.
17 - VM ioctls: These query and set attributes that affect an entire virtual
19 create virtual cpus (vcpus) and devices.
24 - vcpu ioctls: These query and set attributes that control the operation
25 of a single virtual cpu.
32 - device ioctls: These query and set attributes that control the operation
[all …]
|
| /Documentation/driver-api/usb/ |
| D | usb.rst | 1 .. _usb-hostside-api:
4 The Linux-USB Host Side API
18 That master/slave asymmetry was designed-in for a number of reasons, one
22 distributed auto-configuration since the pre-designated master node
37 USB Host-Side API Model
40 Host-side drivers for USB devices talk to the "usbcore" APIs. There are
41 two. One is intended for *general-purpose* drivers (exposed through
49 - USB supports four kinds of data transfers (control, bulk, interrupt,
54 - The device description model includes one or more "configurations"
60 - From USB 3.0 on configurations have one or more "functions", which
[all …]
|
12