All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	"O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: 17.08 Roadmap
Date: Wed, 19 Apr 2017 01:23:52 +0000	[thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B59A732@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20170414143002.GN3790@6wind.com>

Hi Adrien,

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Adrien Mazarguil
> Sent: Friday, April 14, 2017 10:30 PM
> To: O'Driscoll, Tim
> Cc: dev@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

      reply	other threads:[~2017-04-19  1:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14 13:27 17.08 Roadmap O'Driscoll, Tim
2017-04-14 14:30 ` Adrien Mazarguil
2017-04-19  1:23   ` Lu, Wenzhuo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6A0DE07E22DDAD4C9103DF62FEBC09093B59A732@shsmsx102.ccr.corp.intel.com \
    --to=wenzhuo.lu@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=tim.odriscoll@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.