From: Andrey Vesnovaty <andrey.vesnovaty@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Jerin Jacob <jerinjacobk@gmail.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC v2 0/1] add flow action context API
Date: Mon, 22 Jun 2020 20:09:27 +0300 [thread overview]
Message-ID: <CAOwx9SvAZOxeqbBbkC=NOhbt+_ru1gpsMnuEzHdLTLu92A+=Fg@mail.gmail.com> (raw)
In-Reply-To: <8953907.gaXCrnZTga@thomas>
On Mon, Jun 22, 2020 at 6:22 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> 20/06/2020 15:32, Andrey Vesnovaty:
> > Hi, and thanks a lot for your RFC v1 comments.
> >
> > RFC v2 emphasize the intent for sharing the flow action:
> > * The term 'action context' was unclear and replaced with
> > 'shared action'.
> > * RFC v2 subject became 'add flow shared action API'.
> > * all proposed APIs renamed according the above.
> >
> > The new shared action is an independent entity decoupled from any flow
> > while any flow can reuse such an action. Please go over the RFC
> > description, it was almost entirely rewritten.
> >
> > @Jerin Jacob:
> > Thanks again for your comments, it made me admit that v1 description was
> > incomplete & unclear. I hope v2 will be better at least in terms of
> > clarity.
> > @Thomas Monjalon:
> > rte_flow_action_ctx_modify() -> rte_flow_action_ctx_modify()
>
> I guess it is a typo.
> I see the name "rte_flow_shared_action_update" in the patch
>
> Right, a typo. Should be:
rte_flow_action_ctx_modify() -> rte_flow_shared_action_update ()
next prev parent reply other threads:[~2020-06-22 17:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 9:18 [dpdk-dev] [RFC] " Andrey Vesnovaty
2020-06-03 10:02 ` Thomas Monjalon
2020-06-04 11:12 ` Andrey Vesnovaty
2020-06-04 17:23 ` Thomas Monjalon
2020-06-05 8:30 ` Bruce Richardson
2020-06-05 8:33 ` Thomas Monjalon
2020-06-03 10:53 ` Jerin Jacob
2020-06-04 11:25 ` Andrey Vesnovaty
2020-06-04 12:36 ` Jerin Jacob
2020-06-04 15:57 ` Andrey Vesnovaty
2020-06-09 16:01 ` Jerin Jacob
2020-06-20 13:32 ` [dpdk-dev] [RFC v2 0/1] " Andrey Vesnovaty
2020-06-22 15:22 ` Thomas Monjalon
2020-06-22 17:09 ` Andrey Vesnovaty [this message]
2020-06-26 11:44 ` Jerin Jacob
2020-06-28 8:44 ` Andrey Vesnovaty
2020-06-28 13:42 ` Jerin Jacob
2020-06-29 10:22 ` Andrey Vesnovaty
2020-06-30 9:52 ` Jerin Jacob
2020-07-01 9:24 ` Andrey Vesnovaty
2020-07-01 10:34 ` Jerin Jacob
2020-06-20 13:32 ` [dpdk-dev] [RFC v2 1/1] add flow shared action API Andrey Vesnovaty
2020-07-02 0:24 ` Stephen Hemminger
2020-07-02 7:20 ` Ori Kam
2020-07-02 8:06 ` Andrey Vesnovaty
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='CAOwx9SvAZOxeqbBbkC=NOhbt+_ru1gpsMnuEzHdLTLu92A+=Fg@mail.gmail.com' \
--to=andrey.vesnovaty@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinjacobk@gmail.com \
--cc=thomas@monjalon.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).