Hi Adrien,
>On Wed, Mar 15, 2017 at 02:29:44PM +0000, Le Scouarnec Nicolas wrote:
>> Overall, as a user, I feel one difficulty/complexity in using the API comes
>> from the need to
>> specify both the stack of protocol (in type) and at each level the "next
>>
Hi Adrien,
> > > > And about the tpid, ethertype. I have a thought that why we need it as
> > > > it's
> > > duplicate with the item type. I think the initial design is just
> > > following the IEEE
> > > spec to define the structures so we will not miss anything. But why not
> > > do some
> >
My response is inline bellow, and further comment on the code excerpt also
From: Lu, Wenzhuo
Sent: Wednesday, March 8, 2017 4:16 AM
To: Le Scouarnec Nicolas; dev@dpdk.org; Adrien Mazarguil
(adrien.mazarg...@6wind.com)
Cc: Yigit, Ferruh
Subject: RE: Issues with ixgbe and rte_flow
>>
Dear all,
I have been using the new API rte_flow to program filtering on an X540 (ixgbe)
NIC. My goal is to send packets from different VLANs to different queues
(filtering which should be supported by flow director as far as I understand).
I enclosed the setup code at the bottom of this email.
4 matches
Mail list logo
