All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: "Zhao1, Wei" <wei.zhao1@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [RFC v2] Generic flow director/filtering/classification API
Date: Mon, 10 Oct 2016 15:19:27 +0200	[thread overview]
Message-ID: <20161010131927.GK17252@6wind.com> (raw)
In-Reply-To: <A2573D2ACFCADC41BB3BE09C6DE313CA01FDBBB5@PGSMSX103.gar.corp.intel.com>

Hi Wei,

On Mon, Oct 10, 2016 at 09:42:53AM +0000, Zhao1, Wei wrote:
> Hi Adrien Mazarguil,
> 
> In your v2 version of rte_flow.txt , there is an action type RTE_FLOW_ACTION_TYPE_MARK,  but there is no definition of struct rte_flow_action_mark.
> And there is  an definition of struct rte_flow_action_id. Is it a typo or other usage?
> 
> Thank you.
> 
> struct rte_flow_action_id {
> 	uint32_t id; /**< 32 bit value to return with packets. */
> };

That is indeed a mistake, this struct should be named
"rte_flow_action_mark". I'll fix it for the next update, thanks.

-- 
Adrien Mazarguil
6WIND

  reply	other threads:[~2016-10-10 13:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10  9:42 [RFC v2] Generic flow director/filtering/classification API Zhao1, Wei
2016-10-10 13:19 ` Adrien Mazarguil [this message]
2016-10-11  1:47   ` Zhao1, Wei
2016-10-11  8:21     ` Adrien Mazarguil
2016-10-12  2:38       ` Zhao1, Wei
  -- strict thread matches above, loose matches on Subject: below --
2016-07-05 18:16 [RFC] " Adrien Mazarguil
2016-08-19 19:32 ` [RFC v2] " Adrien Mazarguil
2016-08-22 18:30   ` John Fastabend
2016-09-29 17:10   ` Adrien Mazarguil
2016-10-31  7:19     ` Zhang, Helin
2016-11-02 11:13       ` Adrien Mazarguil
2016-11-08  1:31         ` Zhang, Helin
2016-11-09 11:07           ` Adrien Mazarguil

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=20161010131927.GK17252@6wind.com \
    --to=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=wei.zhao1@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.