Home
last modified time | relevance | path

Searched refs:bound (Results 1 – 25 of 64) sorted by relevance

123

/dpdk/lib/eal/common/
H A Deal_common_memzone.c67 unsigned int bound) in memzone_reserve_aligned_thread_unsafe() argument
129 if (bound != 0 && (requested_len > bound || !rte_is_power_of_2(bound))) { in memzone_reserve_aligned_thread_unsafe()
154 if (len == 0 && bound == 0) { in memzone_reserve_aligned_thread_unsafe()
161 requested_len = bound; in memzone_reserve_aligned_thread_unsafe()
164 flags, align, bound, contig); in memzone_reserve_aligned_thread_unsafe()
205 unsigned int flags, unsigned int align, unsigned int bound) in rte_memzone_reserve_thread_safe() argument
216 name, len, socket_id, flags, align, bound); in rte_memzone_reserve_thread_safe()
219 bound, mz); in rte_memzone_reserve_thread_safe()
233 unsigned flags, unsigned align, unsigned bound) in rte_memzone_reserve_bounded() argument
236 align, bound); in rte_memzone_reserve_bounded()
H A Dmalloc_heap.c396 size_t bound, bool contig) in try_expand_heap_primary() argument
416 bound, contig, ms, n_segs); in try_expand_heap_primary()
467 size_t bound, bool contig) in try_expand_heap_secondary() argument
477 req.alloc_req.bound = bound; in try_expand_heap_secondary()
507 flags, align, bound, contig); in try_expand_heap()
616 align, bound, contig)) in alloc_more_mem_on_socket()
635 align, bound, contig)) in alloc_more_mem_on_socket()
645 size_t bound, bool contig) in malloc_heap_alloc_on_heap_id() argument
691 bound, contig)) { in malloc_heap_alloc_on_heap_id()
749 bound, contig); in malloc_heap_alloc()
[all …]
H A Dmalloc_mp.h37 size_t bound; member
80 int socket, unsigned int flags, size_t align, size_t bound,
H A Dmalloc_elem.c220 size_t bound, bool contig) in elem_start_pt() argument
229 const size_t bmask = ~(bound - 1); in elem_start_pt()
238 end_pt = RTE_ALIGN_FLOOR(end_pt, bound); in elem_start_pt()
281 size_t bound, bool contig) in malloc_elem_can_hold() argument
283 return elem_start_pt(elem, size, align, bound, contig) != NULL; in malloc_elem_can_hold()
429 size_t bound, bool contig) in malloc_elem_alloc() argument
431 struct malloc_elem *new_elem = elem_start_pt(elem, size, align, bound, in malloc_elem_alloc()
H A Dmalloc_heap.h38 size_t align, size_t bound, bool contig);
H A Dmalloc_elem.h339 unsigned int align, size_t bound, bool contig);
347 unsigned int align, size_t bound, bool contig);
/dpdk/doc/guides/sample_app_ug/
H A Dkernel_nic_interface.rst110 the KNI kernel thread(s) are bound to for each physical port.
149 will be created for each lcore ID specified, bound to the physical port
155 thread will be bound to the first ``lcore_kthread`` lcore ID specified.
166 interface ``vEth1_0`` with the kernel thread bound to lcore 9.
177 ``vEth1_0``/``vEth1_1`` bound to physical port 1.
179 The kernel thread for each interface will be bound as follows:
181 * ``vEth0_0`` - bound to lcore 8.
182 * ``vEth0_1`` - bound to lcore 10.
183 * ``vEth1_0`` - bound to lcore 9.
184 * ``vEth1_1`` - bound to lcore 11
[all …]
/dpdk/drivers/event/dlb2/pf/base/
H A Ddlb2_hw_types.h85 u32 bound; member
91 return list->bound - list->base - list->offset; in dlb2_freelist_count()
214 const u32 bound[] = {16, 8, 4, 2, 1}; in dlb2_sn_group_alloc_slot() local
217 for (i = 0; i < bound[group->mode]; i++) { in dlb2_sn_group_alloc_slot()
/dpdk/doc/guides/linux_gsg/
H A Dlinux_drivers.rst15 and network ports should be bound to that driver.
30 …It is recommended that ``vfio-pci`` be used as the kernel module for DPDK-bound ports in all cases.
36 and instead be bound to the ``vfio-pci`` kernel module before the application is run.
57 but physical devices may require either all ports bound to VFIO,
58 or some of them bound to VFIO while others not being bound to anything at all.
188 After the PF is bound to ``vfio-pci`` module,
190 and these VFs will be bound to ``vfio-pci`` module automatically.
192 When the PF is bound to ``vfio-pci``,
364 Therefore, devices for use by DPDK should be bound to the ``vfio-pci`` kernel module
370 If the devices used for DPDK are bound to a UIO-based kernel module,
H A Dlinux_eal_parameters.rst28 Create ``/dev/uioX`` files for devices bound to igb_uio kernel driver
41 Use specified interrupt mode for devices bound to VFIO kernel driver.
45 Use specified VF token for devices bound to VFIO kernel driver.
/dpdk/doc/guides/tools/
H A Ddevbind.rst64 …can be used with VFIO on its own, but physical devices will require either all ports bound to VFIO,
65 or some of them bound to VFIO while others not being bound to anything at all.
/dpdk/doc/guides/bbdevs/
H A Dacc100.rst91 FEC device first needs to be bound to one of these linux drivers through DPDK.
100 The igb_uio driver may be bound to the PF PCI device using one of two methods:
103 1. PCI functions (physical or virtual, depending on the use case) can be bound to
124 In a similar way the ACC100 5G/4G FEC PF may be bound with vfio-pci as any PCIe device.
150 Afterwards, all VFs must be bound to appropriate UIO drivers as required, same
H A Dfpga_5gnr_fec.rst76 to be bound to one of these linux drivers through DPDK.
85 The igb_uio driver may be bound to the PF PCI device using one of two methods:
88 1. PCI functions (physical or virtual, depending on the use case) can be bound to
108 In the same way the FPGA 5GNR FEC PF can be bound with vfio, but vfio driver does not
135 Afterwards, all VFs must be bound to appropriate UIO drivers as required, same
H A Dfpga_lte_fec.rst75 to be bound to one of these linux drivers through DPDK.
84 The igb_uio driver may be bound to the PF PCI device using one of two methods:
87 1. PCI functions (physical or virtual, depending on the use case) can be bound to
107 In the same way the FPGA LTE FEC PF can be bound with vfio, but vfio driver does not
134 Afterwards, all VFs must be bound to appropriate UIO drivers as required, same
/dpdk/lib/eal/include/
H A Drte_memzone.h267 unsigned flags, unsigned align, unsigned bound);
H A Drte_eal_trace.h239 unsigned int flags, unsigned int align, unsigned int bound,
246 rte_trace_point_emit_u32(bound);
/dpdk/doc/guides/nics/
H A Dnfp.rst68 bound to ``igb_uio`` or ``vfio-pci`` kernel drivers. Future DPDK versions will
152 same time because the VFs require the PF being bound to the NFP PF Linux
179 -k option shows the device driver, if any, that devices are bound to.
181 bound to nfp_netvf driver.
H A Dcxgbe.rst421 #. Get the PCI bus addresses of the interfaces bound to cxgb4 driver:
436 Both the interfaces of a Chelsio 2-port adapter are bound to the
498 #. Get the PCI bus addresses of the interfaces bound to cxgb4 driver:
513 Both the interfaces of a Chelsio 2-port adapter are bound to the
625 In the example above, a Chelsio T520-CR card is bound to a t5nex0 instance.
715 #. Get the PCI bus addresses of the interfaces bound to t5nex driver:
727 In the above example, the t5nex0 is bound to 2:0:4 bus address.
731 Both the interfaces of a Chelsio 2-port adapter are bound to the
/dpdk/app/test/
H A Dtest_memzone.c774 uint32_t bound) in check_memzone_bounded() argument
779 bmask = ~((rte_iova_t)bound - 1); in check_memzone_bounded()
782 align, bound)) == NULL) { in check_memzone_bounded()
810 __func__, mz->name, bound); in check_memzone_bounded()
/dpdk/doc/guides/dmadevs/
H A Didxd.rst41 To use an Intel\ |reg| DSA device bound to the IDXD kernel driver, the device must first be configu…
113 The HW devices to be used will need to be bound to a user-space IO driver for use.
123 For devices bound to a suitable DPDK-supported VFIO/UIO driver, the HW devices will
135 For devices bound to the IDXD kernel driver,
H A Dhisilicon.rst22 Kunpeng DMA devices will need to be bound to a suitable DPDK-supported
H A Dioat.rst41 Intel\ |reg| IOAT devices will need to be bound to a suitable DPDK-supported
56 For devices bound to a suitable DPDK-supported driver (``vfio-pci``), the HW
/dpdk/doc/guides/rawdevs/
H A Dioat.rst53 or be bound to a user-space IO driver for use.
60 To use a Intel\ |reg| DSA device bound to the IDXD kernel driver, the device must first be configur…
107 The HW devices to be used will need to be bound to a user-space IO driver for use.
117 For devices bound to a suitable DPDK-supported VFIO/UIO driver, the HW devices will
129 For devices bound to the IDXD kernel driver,
/dpdk/doc/guides/regexdevs/
H A Dcn9k.rst30 The CN9K REE devices will need to be bound to a user-space IO driver
/dpdk/doc/guides/platform/
H A Dcnxk.rst95 1. PFx and PFx-VF0 bound to Linux netdev driver.
96 2. PFx-VF1 ethdev driver bound to the first DPDK application.
97 3. PFy ethdev driver, PFy-VF0 ethdev driver, PFz eventdev driver, PFm-VF0 cryptodev driver bound to…
108 where even VF bound to the first domain and odd VF bound to the second domain.

123