458485eb21
Some of the HW has support for choosing memory pools based on the packet's size. This is often useful for saving the memory where the application can create a different pool to steer the specific size of the packet, thus enabling more efficient usage of memory. For example, let's say HW has a capability of three pools, - pool-1 size is 2K - pool-2 size is > 2K and < 4K - pool-3 size is > 4K Here, pool-1 can accommodate packets with sizes < 2K pool-2 can accommodate packets with sizes > 2K and < 4K pool-3 can accommodate packets with sizes > 4K With multiple mempool capability enabled in SW, an application may create three pools of different sizes and send them to PMD. Allowing PMD to program HW based on the packet lengths. So that packets with less than 2K are received on pool-1, packets with lengths between 2K and 4K are received on pool-2 and finally packets greater than 4K are received on pool-3. Signed-off-by: Hanumanth Pothula <hpothula@marvell.com> Signed-off-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru> |
||
---|---|---|
.. | ||
ethdev_driver.c | ||
ethdev_driver.h | ||
ethdev_pci.h | ||
ethdev_private.c | ||
ethdev_private.h | ||
ethdev_profile.c | ||
ethdev_profile.h | ||
ethdev_trace_points.c | ||
ethdev_vdev.h | ||
meson.build | ||
rte_class_eth.c | ||
rte_cman.h | ||
rte_dev_info.h | ||
rte_eth_ctrl.h | ||
rte_ethdev_cman.c | ||
rte_ethdev_core.h | ||
rte_ethdev_trace_fp.h | ||
rte_ethdev_trace.h | ||
rte_ethdev.c | ||
rte_ethdev.h | ||
rte_flow_driver.h | ||
rte_flow.c | ||
rte_flow.h | ||
rte_mtr_driver.h | ||
rte_mtr.c | ||
rte_mtr.h | ||
rte_tm_driver.h | ||
rte_tm.c | ||
rte_tm.h | ||
sff_8079.c | ||
sff_8472.c | ||
sff_8636.c | ||
sff_8636.h | ||
sff_common.c | ||
sff_common.h | ||
sff_telemetry.c | ||
sff_telemetry.h | ||
version.map |