From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: Xiaoyu Min <jackmin@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [RFC v2 2/3] ethdev: add flow api actions to modify TCP/UDP port numbers
Date: Wed, 19 Sep 2018 20:46:10 +0530 [thread overview]
Message-ID: <20180919151609.GB6366@chelsio.com> (raw)
In-Reply-To: <20180918092910.igibtq2ahsllizx5@MTBC-JACKMIN.mtl.com>
On Tuesday, September 09/18/18, 2018 at 14:59:10 +0530, Xiaoyu Min wrote:
> >
> > diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
> > b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
> > index 638331c17..f60be0862 100644
> > --- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
> > +++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
> > @@ -3713,6 +3713,14 @@ This section lists supported actions and their
> > attributes, if any.
> >
> > - ``ipv6_addr``: New IPv6 destination address.
> >
> > +- ``of_set_tp_src``: Set a new TCP/UDP source port number.
> should be set_tp_src :-)
> > +
> > + - ``port``: New TCP/UDP source port number.
> > +
> > +- ``of_set_tp_dst``: Set a new TCP/UDP destination port number.
> set_tp_dst
> > + - ``port``: New TCP/UDP destination port number.
> > +
> > Destroying flow rules
> > ~~~~~~~~~~~~~~~~~~~~~
> >
>
>
> > static int
> > diff --git a/lib/librte_ethdev/rte_flow.h b/lib/librte_ethdev/rte_flow.h
> > index 48c3c606e..c80771b25 100644
> > --- a/lib/librte_ethdev/rte_flow.h
> > +++ b/lib/librte_ethdev/rte_flow.h
> > @@ -1533,6 +1533,20 @@ enum rte_flow_action_type {
> > * See struct rte_flow_action_set_ipv6.
> > */
> > RTE_FLOW_ACTION_TYPE_SET_IPV6_DST,
> > +
> > + /**
> > + * Modify source port in TCP/UDP packets.
> > + *
> > + * See struct rte_flow_action_set_tp.
> > + */
> > + RTE_FLOW_ACTION_TYPE_SET_TP_SRC,
> > +
> > + /**
> > + * Modify destination port in TCP/UDP packets.
> > + *
> > + * See struct rte_flow_action_set_tp.
> > + */
> > + RTE_FLOW_ACTION_TYPE_SET_TP_DST,
> > };
> >
> We need to state the corresponding RTE_FLOW_ITEM_TYPE_(UDP|TCP) should be in pattern
>
Ok. Will update the comment and doc.
Thanks,
Rahul
next prev parent reply other threads:[~2018-09-19 15:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 9:56 [RFC 0/3] ethdev: add IP address and TCP/UDP port rewrite actions to flow API Rahul Lakkireddy
2018-06-22 9:56 ` [RFC 1/3] ethdev: add flow api actions to modify IP addresses Rahul Lakkireddy
2018-06-22 9:56 ` [RFC 2/3] ethdev: add flow api actions to modify TCP/UDP port numbers Rahul Lakkireddy
2018-06-22 9:56 ` [RFC 3/3] net/cxgbe: add flow actions to modify IP and TCP/UDP port address Rahul Lakkireddy
2018-06-26 10:32 ` [RFC 0/3] ethdev: add IP address and TCP/UDP port rewrite actions to flow API Thomas Monjalon
2018-07-02 9:09 ` Jack Min
2018-07-02 12:04 ` Rahul Lakkireddy
2018-07-03 2:27 ` Jack Min
2018-07-03 13:39 ` Rahul Lakkireddy
2018-07-04 1:11 ` Jack Min
2018-07-05 20:16 ` Adrien Mazarguil
2018-07-10 13:14 ` Rahul Lakkireddy
2018-08-01 23:35 ` Jack Min
2018-08-02 14:59 ` Rahul Lakkireddy
2018-08-13 13:36 ` [RFC v2 " Rahul Lakkireddy
2018-08-13 13:36 ` [RFC v2 1/3] ethdev: add flow api actions to modify IP addresses Rahul Lakkireddy
2018-09-18 7:56 ` Xiaoyu Min
2018-09-19 15:14 ` Rahul Lakkireddy
2018-08-13 13:36 ` [RFC v2 2/3] ethdev: add flow api actions to modify TCP/UDP port numbers Rahul Lakkireddy
2018-09-18 9:29 ` Xiaoyu Min
2018-09-19 15:16 ` Rahul Lakkireddy [this message]
2018-08-13 13:36 ` [RFC v2 3/3] net/cxgbe: add flow actions to modify IP and TCP/UDP port address Rahul Lakkireddy
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=20180919151609.GB6366@chelsio.com \
--to=rahul.lakkireddy@chelsio.com \
--cc=dev@dpdk.org \
--cc=jackmin@mellanox.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.