Re: [dpdk-dev] Requirement of minimum Rx burst size for PMDs

2017-10-20 Thread Yongseok Koh
On Fri, Oct 20, 2017 at 03:23:10PM +0300, Andrew Rybchenko wrote: > On 10/20/2017 02:58 PM, Bruce Richardson wrote: > > On Fri, Oct 20, 2017 at 01:07:17PM +0300, Andrew Rybchenko wrote: > > > On 10/20/2017 04:18 AM, Yongseok Koh wrote: > > > > Therefore, how about adding min_rx/tx_burst_sz in struc

Re: [dpdk-dev] Requirement of minimum Rx burst size for PMDs

2017-10-20 Thread Andrew Rybchenko
On 10/20/2017 02:58 PM, Bruce Richardson wrote: On Fri, Oct 20, 2017 at 01:07:17PM +0300, Andrew Rybchenko wrote: On 10/20/2017 04:18 AM, Yongseok Koh wrote: Therefore, how about adding min_rx/tx_burst_sz in struct rte_eth_dev_info and have PMDs fill it in on dev_ops->dev_infos_get() so as to m

Re: [dpdk-dev] Requirement of minimum Rx burst size for PMDs

2017-10-20 Thread Bruce Richardson
On Fri, Oct 20, 2017 at 01:07:17PM +0300, Andrew Rybchenko wrote: > On 10/20/2017 04:18 AM, Yongseok Koh wrote: > > Therefore, how about adding min_rx/tx_burst_sz in struct rte_eth_dev_info > > and > > have PMDs fill it in on dev_ops->dev_infos_get() so as to make apps comply > > with > > it. >

Re: [dpdk-dev] Requirement of minimum Rx burst size for PMDs

2017-10-20 Thread Andrew Rybchenko
On 10/20/2017 04:18 AM, Yongseok Koh wrote: Therefore, how about adding min_rx/tx_burst_sz in struct rte_eth_dev_info and have PMDs fill it in on dev_ops->dev_infos_get() so as to make apps comply with it. Just for my understand, what should happen if application wants to send only one packet?

Re: [dpdk-dev] Requirement of minimum Rx burst size for PMDs

2017-10-20 Thread Bruce Richardson
On Fri, Oct 20, 2017 at 01:18:18AM +, Yongseok Koh wrote: > Hi, > > In some rx_burst functions, especially for vectorized ones (e.g. > i40e_rxtx_vec* > or mlx5_rxtx_vec*), there's actually a requirement of min burst size. > > As it manipulates 4 packets simultaneously in a loop, if nb_pkts o

[dpdk-dev] Requirement of minimum Rx burst size for PMDs

2017-10-19 Thread Yongseok Koh
Hi, In some rx_burst functions, especially for vectorized ones (e.g. i40e_rxtx_vec* or mlx5_rxtx_vec*), there's actually a requirement of min burst size. As it manipulates 4 packets simultaneously in a loop, if nb_pkts of rte_eth_rx_burst() is less than 4, it just returns without sending a packet