[dpdk-dev] 17.08 Roadmap
Lu, Wenzhuo
wenzhuo.lu at intel.com
Wed Apr 19 03:23:52 CEST 2017
Hi Adrien,
> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Adrien Mazarguil
> Sent: Friday, April 14, 2017 10:30 PM
> To: O'Driscoll, Tim
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] 17.08 Roadmap
>
> On Fri, Apr 14, 2017 at 01:27:13PM +0000, O'Driscoll, Tim wrote:
> >
> > API to Configure Queue Regions for RSS: This provides support for
> configuration of queue regions for RSS, so that different traffic classes or
> different packet classification types to be separated into different queues.
> This will be implemented for I40E.
>
> About this last topic, do you mean devising a new API is necessary or do you
> plan to implement it through rte_flow? I'm asking as it looks like this is what
> the rte_flow RSS action is defined for, see [1]. The mlx5 PMD adds support
> for it in 17.05 [2].
Yes. We'll try to use rte_flow if appropriate. And this RSS action is planned to be used.
>
> I also intend to submit a few changes to rte_flow:
>
> - VLAN item fix (according to this thread [3]). Impacts PMDs that implement
> the VLAN and associated items. Not sure it can be accepted or 17.08 due to
> ABI breakage, but it will be submitted regardless.
BTW,
Ixgbe has removed the tpid check. http://dpdk.org/dev/patchwork/patch/23637/
I don't find another one using tpid.
So, PMD should be ready. We can remove the tpid from rte now.
>
> - A new isolated operation mode for rte_flow, guaranteeing applications can
> expect to receive packets from the flow rules they define *only* for
> complete control. No more "default" RX rules, RSS and so on. It means
> PMDs
> are free to reassign these resources to flow rules. No planned ABI
> breakage.
>
> [1] http://dpdk.org/doc/guides/prog_guide/rte_flow.html#action-rss
> [2] http://dpdk.org/browse/next/dpdk-next-
> net/commit/?id=1bfb7bb4423349ab13decead0af8ffd006e8e398
> [3] http://dpdk.org/ml/archives/dev/2017-March/060231.html
>
> --
> Adrien Mazarguil
> 6WIND
More information about the dev
mailing list