OVS DPDK DMA-Dev library/Design Discussion

[Mcnamara, John]

> -----Original Message-----
> From: Ilya Maximets <i.maximets at ovn.org>
> Sent: Monday, April 25, 2022 10:46 PM
> To: Mcnamara, John <john.mcnamara at intel.com>; Hu, Jiayu
> <jiayu.hu at intel.com>; Maxime Coquelin <maxime.coquelin at redhat.com>; Van
> Haaren, Harry <harry.van.haaren at intel.com>; Morten Brørup
> <mb at smartsharesystems.com>; Richardson, Bruce
> <bruce.richardson at intel.com>
> Cc: i.maximets at ovn.org; Pai G, Sunil <sunil.pai.g at intel.com>; Stokes,
> Ian <ian.stokes at intel.com>; Ferriter, Cian <cian.ferriter at intel.com>;
> ovs-dev at openvswitch.org; dev at dpdk.org; O'Driscoll, Tim
> <tim.odriscoll at intel.com>; Finn, Emma <emma.finn at intel.com>
> Subject: Re: OVS DPDK DMA-Dev library/Design Discussion
> 
> ...
> 
> FWIW, I think it makes sense to PoC and test options that are going to
> be simply unavailable going forward if not explored now.
> Especially because we don't have any good solutions anyway ("Deferral
> of Work" is architecturally wrong solution for OVS).

I agree that there is value in doing PoCs and we have been doing that for over a year based on different proposals and none of them show the potential of the Deferral of Work approach. It isn't productive to keep building PoCs indefinitely; at some point we need to make progress with merging a specific solution upstream.


> > Let's have another call so that we can move towards a single solution
> that the DPDK and OVS communities agree on. I'll set up a call for next
> week in a similar time slot to the previous one.
> 
> Is there any particular reason we can't use a mailing list to discuss
> that topic further?

The discussion can continue on the mailing list. It just seemed more efficient and interactive to discuss this in a meeting.

John
--