| /f-stack/freebsd/contrib/device-tree/Bindings/display/ti/ |
| H A D | ti,am65x-dss.yaml | 17 supports DPI format. The fist plane is full video plane with all 18 features and the second is a "lite plane" without scaling support. 29 - description: VIDL1 light video plane 30 - description: VID video plane
|
| H A D | ti,j721e-dss.yaml | 30 - description: VIDL1 light video plane 1 31 - description: VIDL2 light video plane 2 32 - description: VID1 video plane 1 33 - description: VID1 video plane 2
|
| H A D | ti,k2g-dss.yaml | 16 SubSystem. It has only one output port and video plane. The 27 - description: VID1 video plane 1
|
| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | pipeline.rst | 111 Each data plane thread runs one or several pipelines previously assigned to it in round-robin order… 116 2. *Message handling task*: Periodically, the data plane thread pauses the packet processing task a… 117 …messages send by the main thread. Examples: add/remove pipeline to/from current data plane thread,… 118 …to/from given table of a specific pipeline owned by the current data plane thread, read statistics…
|
| H A D | ip_pipeline.rst | 127 Each data plane thread runs one or several pipelines previously assigned to it in round-robin order… 132 2. *Message handling task*: Periodically, the data plane thread pauses the packet processing task a… 133 …messages send by the main thread. Examples: add/remove pipeline to/from current data plane thread,… 134 …to/from given table of a specific pipeline owned by the current data plane thread, read statistics… 550 Enable given pipeline instance for specific data plane thread :: 555 Disable given pipeline instance for specific data plane thread ::
|
| H A D | kernel_nic_interface.rst | 7 The Kernel NIC Interface (KNI) is a DPDK control plane solution that
|
| /f-stack/freebsd/arm/nvidia/drm2/ |
| H A D | tegra_dc.c | 509 struct tegra_plane *plane; in dc_plane_update() local 538 dc_setup_window(sc, plane->index, &win); in dc_plane_update() 549 struct tegra_plane *plane; in dc_plane_disable() local 560 idx = plane->index; in dc_plane_disable() 582 dc_plane_disable(plane); in dc_plane_destroy() 583 drm_plane_cleanup(plane); in dc_plane_destroy() 584 free(plane, DRM_MEM_KMS); in dc_plane_destroy() 1102 struct tegra_plane *plane; in dc_init_planes() local 1106 plane = malloc(sizeof(*plane), DRM_MEM_KMS, M_WAITOK | M_ZERO); in dc_init_planes() 1107 plane->index = i + 1; in dc_init_planes() [all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/display/xlnx/ |
| H A D | xlnx,zynqmp-dpsub.yaml | 103 - description: Video layer, plane 0 (RGB or luma) 104 - description: Video layer, plane 1 (U/V or U) 105 - description: Video layer, plane 2 (V)
|
| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | glossary.rst | 27 The control plane is concerned with the routing of packets and with 45 In contrast to the control plane, the data plane in a network architecture
|
| H A D | writing_efficient_code.rst | 21 This can ease the porting of applications and the development of the configuration plane. 23 Functions such as memcpy() or strcpy() should not be used in the data plane. 37 but it is really not advised to use malloc-like functions in the data plane because 40 If you really need dynamic allocation in the data plane, it is better to use a memory pool of fixed… 180 Performance can be improved by avoiding lock mechanisms in the data plane.
|
| H A D | overview.rst | 12 complete framework for fast packet processing in data plane applications. 45 they may then be used to create the user's data plane application.
|
| H A D | thread_safety_dpdk_functions.rst | 21 Applications operating in the data plane are performance sensitive but
|
| H A D | vhost_lib.rst | 311 the data plane, and ``VHOST_GET_VRING_BASE`` is used as the signal to remove 312 the vhost device from the data plane.
|
| H A D | mempool_lib.rst | 156 * Any application that needs to allocate fixed-sized objects in the data plane and that will be c…
|
| H A D | kernel_nic_interface.rst | 9 …e DPDK Kernel NIC Interface (KNI) allows userspace applications access to the Linux* control plane.
|
| H A D | rcu_lib.rst | 136 A control plane thread can also call this on behalf of a reader thread.
|
| H A D | packet_framework.rst | 1156 to code a complete software switch or data plane application, or in combination with the open-sourc… 1170 * Better control plane interaction: Transaction-oriented table update mechanism that supports mul…
|
| /f-stack/freebsd/contrib/device-tree/Bindings/iio/ |
| H A D | mount-matrix.txt | 60 is projected onto the (x,y) plane of the display panel. 96 ground plane and positive towards magnetic North, (x) is in the ground plane, 98 perpendicular to the ground plane and positive upwards. 130 velocity is defined as orthogonal to the plane of rotation, so if you put the
|
| /f-stack/dpdk/doc/guides/howto/ |
| H A D | flow_bifurcation.rst | 17 the Linux kernel stack). It can direct some traffic, for example data plane 19 plane traffic, to the traditional Linux networking stack.
|
| H A D | debug_troubleshoot.rst | 446 possible data corruption in the data plane.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/media/ |
| H A D | video-interfaces.txt | 112 reference system on the focal plane of the camera module. The origin is 135 with the reference system 'Rs' placed on the camera focal plane: 141 | (o) | ! Camera focal plane
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | bnxt.rst | 76 It can direct some traffic, for example data plane traffic, to DPDK. 77 Rest of the traffic, for example control plane traffic, would be redirected to 658 The feature uses a newly implemented control-plane firmware interface which 962 gateways, control plane processing for Ethernet switches, and network-attached
|
| /f-stack/dpdk/doc/guides/rel_notes/ |
| H A D | release_19_11.rst | 248 user plane. Test and test-crypto-perf applications have been updated for 309 plane (RIB) performance. The data plane (FIB) can be extended with new
|
| /f-stack/dpdk/doc/guides/contributing/ |
| H A D | design.rst | 172 a PF driver is a control plane feature and developers should generally rely on
|
| /f-stack/dpdk/doc/guides/tools/ |
| H A D | cryptoperf.rst | 321 Set PDCP domain to specify Control/user plane.
|