Re: [dpdk-dev] [PATCH v3 05/10] drivers: replace references to blacklist

For fslmc and dpaa Acked-by: Hemant Agrawal

Re: [dpdk-dev] [PATCH 7/7] eal: add lcore hotplug notifications

From ABI  PoV, you are 100%. Is the agreed term 'callback'?, not 'notifier' for example rte_dev_event_callback_register, rte_mem_event_callback_register I did wonder however, if all these cb's would be better handled through a EventDev event notification style approach. Ray K On 10/06/2020 15

Re: [dpdk-dev] [PATCH 6/7] eal: dump lcores

On 10/06/2020 15:45, David Marchand wrote: > Add a little helper to dump all lcores. > > Signed-off-by: David Marchand > --- > lib/librte_eal/common/eal_common_lcore.c | 32 +++ > lib/librte_eal/common/eal_common_thread.c | 16 > lib/librte_eal/common/eal_threa

Re: [dpdk-dev] [PATCH 5/7] eal: register non-EAL threads as lcore

On 10/06/2020 15:45, David Marchand wrote: > DPDK allows calling some part of its API from a non-EAL thread but this > has some limitations. > OVS (and other applications) has its own thread management but still > want to avoid such limitations by hacking RTE_PER_LCORE(_lcore_id) and > faking EAL

Re: [dpdk-dev] [PATCH 2/7] eal: fix multiple definition of per lcore thread id

On 10/06/2020 15:45, David Marchand wrote: > Because of the inline accessor + static declaration in rte_gettid(), > we end up with multiple symbols for RTE_PER_LCORE(_thread_id). > Each compilation unit will pay a cost when accessing this information > for the first time. > > $ nm build/app/dpdk-

Re: [dpdk-dev] [PATCH v1 0/8] mlx5 PMD multi OS support - part #2

Hi, > -Original Message- > From: Matan Azrad > Sent: Sunday, June 14, 2020 11:21 AM > To: Ophir Munk ; dev@dpdk.org; Raslan > Darawsheh > Subject: RE: [PATCH v1 0/8] mlx5 PMD multi OS support - part #2 > > > > From: Ophir Munk: > > This patch series is part of preparing mlx5 PMD to co

<    1   2