Re: Reuse Of lcore after returning from its worker thread

But how the state is changed to WAIT once the worker thread function returned On Tue, 26 Apr, 2022, 8:26 pm Stephen Hemminger, wrote: > On Wed, 20 Apr 2022 17:52:20 +0530 > Ansar Kannankattil wrote: > > > Hi, > > As per my understanding "*rte_eal_wait_lcore" *is

Reuse Of lcore after returning from its worker thread

Hi, As per my understanding "*rte_eal_wait_lcore" *is a blocking call in case of lcore state running. 1. Is there any direct way to reuse the lcore which we returned from a worker thread? 2. Technically is there any issue in reusing the lcore by some means?

Re: Can I use rte_pktmbuf_chain to chain multiple mbuffs for calling only single tx_eth_burst API

; >> On 2/9/2022 6:03 PM, Ansar Kannankattil wrote: > >>> Hi > >>> My intention is to decrease the number of rte_tx_eth_burst calls, I > know that mentioning nb_pkts will result in sending multiple packets in a > single call. > >>> But providing nb_pkts=

Can I use rte_pktmbuf_chain to chain multiple mbuffs for calling only single tx_eth_burst API

Hi My intention is to decrease the number of rte_tx_eth_burst calls, I know that mentioning nb_pkts will result in sending multiple packets in a single call. But providing nb_pkts=1 and posting a head mbuff having number of mbuffs linked with it will results sending multiple packets If not, what is