Re: [dpdk-dev] Backporting rte_intr_ack

2019-11-22 Thread Kevin Traynor
On 22/11/2019 15:24, Thomas Monjalon wrote: > 22/11/2019 16:12, Kevin Traynor: >> On 19/11/2019 10:40, Thomas Monjalon wrote: >>> 14/10/2019 17:55, David Marchand: The api rte_intr_ack that has been introduced to fix a race condition observed with (at least) qede drivers/hw. This is

Re: [dpdk-dev] Backporting rte_intr_ack

2019-11-22 Thread Thomas Monjalon
22/11/2019 16:12, Kevin Traynor: > On 19/11/2019 10:40, Thomas Monjalon wrote: > > 14/10/2019 17:55, David Marchand: > >> The api rte_intr_ack that has been introduced to fix a race condition > >> observed with (at least) qede drivers/hw. > >> This is an experimental api in master but it still fixe

Re: [dpdk-dev] Backporting rte_intr_ack

2019-11-22 Thread Kevin Traynor
On 19/11/2019 10:40, Thomas Monjalon wrote: > 14/10/2019 17:55, David Marchand: >> The api rte_intr_ack that has been introduced to fix a race condition >> observed with (at least) qede drivers/hw. >> This is an experimental api in master but it still fixes a problem, so >> I'd like to see this in

Re: [dpdk-dev] Backporting rte_intr_ack

2019-11-19 Thread Thomas Monjalon
14/10/2019 17:55, David Marchand: > The api rte_intr_ack that has been introduced to fix a race condition > observed with (at least) qede drivers/hw. > This is an experimental api in master but it still fixes a problem, so > I'd like to see this in stable branches. This is more a driver interface

[dpdk-dev] Backporting rte_intr_ack

2019-10-14 Thread David Marchand
Hello guys, The api rte_intr_ack that has been introduced to fix a race condition observed with (at least) qede drivers/hw. This is an experimental api in master but it still fixes a problem, so I'd like to see this in stable branches. Opinions? Thanks. -- David Marchand