[ovs-dev] [PATCH v2 6/8] netdev-dpdk: retry with queue action

Chandran, Sugesh sugesh.chandran at intel.com
Mon Sep 11 08:56:54 UTC 2017



Regards
_Sugesh


> -----Original Message-----
> From: Yuanhan Liu [mailto:yliu at fridaylinux.org]
> Sent: Monday, September 11, 2017 8:56 AM
> To: Chandran, Sugesh <sugesh.chandran at intel.com>
> Cc: dev at openvswitch.org
> Subject: Re: [ovs-dev] [PATCH v2 6/8] netdev-dpdk: retry with queue action
> 
> On Mon, Sep 11, 2017 at 07:42:19AM +0000, Chandran, Sugesh wrote:
> >
> >
> > Regards
> > _Sugesh
> >
> >
> > > -----Original Message-----
> > > From: ovs-dev-bounces at openvswitch.org [mailto:ovs-dev-
> > > bounces at openvswitch.org] On Behalf Of Yuanhan Liu
> > > Sent: Tuesday, September 5, 2017 10:23 AM
> > > To: dev at openvswitch.org
> > > Subject: [ovs-dev] [PATCH v2 6/8] netdev-dpdk: retry with queue
> > > action
> > >
> > > From: Finn Christensen <fc at napatech.com>
> > >
> > > AFAIK, most (if not all) NICs (including Mellanox and Intel) do not
> > > support a pure MARK action.  It's required to be used together with
> > > some other actions, like QUEUE.
> > >
> > > To workaround it, retry with a queue action when first try failed.
> > [Sugesh] This means a NIC that doesn't support pure MARK, will do
> > every flow install twice no matter how many times the flow install failed
> before for the same reason.
> > The retry can be avoided if we know what a port/NIC can support. It
> > leads to a need of feature discovery of a NIC at the init time.
> 
> I believe the reply I made to Simon answered all questions you asked above.
[Sugesh] Thanks!

> 
> 	--yliu


More information about the dev mailing list