[dpdk-dev] rte_eth_rx_burst only returns up to 32 packets

On Aug 29, 2015 16:55, "Masood Moshref Javadi" wrote: > > Thanks a lot. > > So I assume the only way to see if there are more than 256 packets in the > queue is to count them using rte_eth_rx_count Sorry for bulging in but i think Masood rose a very important general question here, which is: how

[dpdk-dev] rte_eth_rx_burst only returns up to 32 packets

Thanks a lot. So I assume the only way to see if there are more than 256 packets in the queue is to count them using rte_eth_rx_count On Aug 28, 2015 8:32 PM, "Gaohaifeng (A)" wrote: > Please see _rece_raw_pkts_vec function. > > Here is part of its comments may explain this question > /* > * v

[dpdk-dev] rte_eth_rx_burst only returns up to 32 packets

Please see _rece_raw_pkts_vec function. Here is part of its comments may explain this question /* * vPMD receive routine, now only accept (nb_pkts == RTE_IXGBE_VPMD_RX_BURST) * in one loop * * Notice: * - nb_pkts < RTE_IXGBE_VPMD_RX_BURST, just return no packet * - nb_pkts > RTE_IXGBE_VPMD_

[dpdk-dev] [PATCH v4 2/2] Filling speed capability bitmaps in the PMDs

Added speed capabilities to all pmds supporting physical NICs: * e1000 * ixgbe * i40 * mlx4 * fm10k Signed-off-by: Marc Sune --- drivers/net/e1000/em_ethdev.c| 6 ++ drivers/net/e1000/igb_ethdev.c | 6 ++ drivers/net/fm10k/fm10k_ethdev.c | 3 +++ drivers/net/i40e/i40e_ethdev.c

[dpdk-dev] [PATCH v4 1/2] Added ETH_SPEED_ bitmap in rte_eth_dev_info

Currently there was no way to recover all the supported speeds of a certain ether device. This commit adds a speed capability bitmap to rte_eth_dev_info struct, to be filled by PMDs. It also renames ETH_LINK_SPEED_XXX to ETH_SPEED, in order to unify speed capabilities and link speeds. It also adds

[dpdk-dev] [PATCH v4 0/2] ethdev: add port speed capability bitmap

The current rte_eth_dev_info abstraction does not provide any mechanism to get the supported speed(s) of an ethdev. For some drivers (e.g. ixgbe), an educated guess can be done based on the driver's name (driver_name in rte_eth_dev_info), see: http://dpdk.org/ml/archives/dev/2013-August/000412.ht

[dpdk-dev] [PATCH v3 2/2] Filling speed capability bitmaps in the PMDs

Added speed capabilities to all pmds supporting physical NICs: * e1000 * ixgbe * i40 * mlx4 * fm10k Signed-off-by: Marc Sune --- drivers/net/e1000/em_ethdev.c| 6 ++ drivers/net/e1000/igb_ethdev.c | 6 ++ drivers/net/fm10k/fm10k_ethdev.c | 3 +++ drivers/net/i40e/i40e_ethdev.c

[dpdk-dev] [PATCH v3 1/2] Added ETH_SPEED_ bitmap in rte_eth_dev_info

Currently there was no way to recover all the supported speeds of a certain ether device. This commit adds a speed capability bitmap to rte_eth_dev_info struct, to be filled by PMDs. It also renames ETH_LINK_SPEED_XXX to ETH_SPEED, in order to unify speed capabilities and link speeds. It also adds

[dpdk-dev] [PATCH v3 0/2] ethdev: add port speed capability bitmap

From: Marc Sune The current rte_eth_dev_info abstraction does not provide any mechanism to get the supported speed(s) of an ethdev. For some drivers (e.g. ixgbe), an educated guess can be done based on the driver's name (driver_name in rte_eth_dev_info), see: http://dpdk.org/ml/archives/dev/201