Re: [dpdk-dev] [RFC v2 3/5] ethdev: copy ethdev 'burst' API into separate structure

2021-09-28 Thread Ananyev, Konstantin
> > > > > > Copy public function pointers (rx_pkt_burst(), etc.) and related > > > pointers to internal data from rte_eth_dev structure into a separate flat > > > array. We can keep it public to still use inline functions for 'fast' > > > calls > > > (like rte_eth_rx_burst(), etc.) to avoid/minim

Re: [dpdk-dev] [RFC v2 3/5] ethdev: copy ethdev 'burst' API into separate structure

2021-09-27 Thread Jerin Jacob
On Thu, Sep 23, 2021 at 11:28 AM Wang, Haiyue wrote: > > > -Original Message- > > From: Ananyev, Konstantin > > Sent: Wednesday, September 22, 2021 22:10 > > To: dev@dpdk.org > > Cc: Li, Xiaoyun ; ano...@marvell.com; > > jer...@marvell.com; > > ndabilpu...@marvell.com; adwiv...@marvell.c

Re: [dpdk-dev] [RFC v2 3/5] ethdev: copy ethdev 'burst' API into separate structure

2021-09-22 Thread Wang, Haiyue
> -Original Message- > From: Ananyev, Konstantin > Sent: Wednesday, September 22, 2021 22:10 > To: dev@dpdk.org > Cc: Li, Xiaoyun ; ano...@marvell.com; > jer...@marvell.com; > ndabilpu...@marvell.com; adwiv...@marvell.com; shepard.sie...@atomicrules.com; > ed.cz...@atomicrules.com; john.m

[dpdk-dev] [RFC v2 3/5] ethdev: copy ethdev 'burst' API into separate structure

2021-09-22 Thread Konstantin Ananyev
Copy public function pointers (rx_pkt_burst(), etc.) and related pointers to internal data from rte_eth_dev structure into a separate flat array. We can keep it public to still use inline functions for 'fast' calls (like rte_eth_rx_burst(), etc.) to avoid/minimize slowdown. The intention is to make