DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dekel Peled <dekelp@mellanox.com>
To: Yongseok Koh <yskoh@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Ori Kam <orika@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: allow flow rule with attribute egress
Date: Wed, 3 Oct 2018 13:02:03 +0000	[thread overview]
Message-ID: <VI1PR05MB42240A6F053B7B59751F9181B6E90@VI1PR05MB4224.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20181003072804.GB21743@mtidpdk.mti.labs.mlnx>

Thanks, PSB.

> -----Original Message-----
> From: Yongseok Koh
> Sent: Wednesday, October 3, 2018 10:28 AM
> To: Dekel Peled <dekelp@mellanox.com>
> Cc: dev@dpdk.org; Shahaf Shuler <shahafs@mellanox.com>; Ori Kam
> <orika@mellanox.com>
> Subject: Re: [PATCH] net/mlx5: allow flow rule with attribute egress
> 
> On Tue, Oct 02, 2018 at 11:06:07PM -0700, Dekel Peled wrote:
> > Thanks, PSB.
> >
> > > -----Original Message-----
> > > From: Yongseok Koh
> > > Sent: Saturday, September 29, 2018 12:24 PM
> > > To: Dekel Peled <dekelp@mellanox.com>
> > > Cc: dev@dpdk.org; Shahaf Shuler <shahafs@mellanox.com>; Ori Kam
> > > <orika@mellanox.com>
> > > Subject: Re: [PATCH] net/mlx5: allow flow rule with attribute egress
> > >
> > > On Thu, Sep 27, 2018 at 05:25:30PM +0300, Dekel Peled wrote:
> > > > This patch complements [1], adding to MLX5 PMD the option to set
> > > > flow rule for egress traffic.
> > > >
> > > > [1] "net/mlx5: support metadata as flow rule criteria"
> > > >     http://mails.dpdk.org/archives/dev/2018-September/113275.html
> > > >
> > > > Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> > > > ---
> > > >  drivers/net/mlx5/mlx5_flow.c       | 54
> > > ++++++++++++++++++++++++++++++++++++++
> > > >  drivers/net/mlx5/mlx5_flow.h       |  6 +++++
> > > >  drivers/net/mlx5/mlx5_flow_dv.c    | 24 ++++++++++-------
> > > >  drivers/net/mlx5/mlx5_flow_verbs.c |  7 ++++-
> > > >  4 files changed, 80 insertions(+), 11 deletions(-)
> > > >
> > > > diff --git a/drivers/net/mlx5/mlx5_flow.c
> > > > b/drivers/net/mlx5/mlx5_flow.c index 9581691..79a06df 100644
> > > > --- a/drivers/net/mlx5/mlx5_flow.c
> > > > +++ b/drivers/net/mlx5/mlx5_flow.c
> > > > @@ -644,6 +644,8 @@ uint32_t mlx5_flow_adjust_priority(struct
> > > rte_eth_dev *dev, int32_t priority,
> > > >   *
> > > >   * @param[in] action_flags
> > > >   *   Bit-fields that holds the actions detected until now.
> > > > + * @param[in] attr
> > > > + *   Attributes of flow that includes this action.
> > > >   * @param[out] error
> > > >   *   Pointer to error structure.
> > > >   *
> > > > @@ -652,6 +654,7 @@ uint32_t mlx5_flow_adjust_priority(struct
> > > rte_eth_dev *dev, int32_t priority,
> > > >   */
> > > >  int
> > > >  mlx5_flow_validate_action_flag(uint64_t action_flags,
> > > > +			       const struct rte_flow_attr *attr,
> > > >  			       struct rte_flow_error *error)  {
> > > >
> > > > @@ -668,6 +671,12 @@ uint32_t mlx5_flow_adjust_priority(struct
> > > rte_eth_dev *dev, int32_t priority,
> > > >  					  RTE_FLOW_ERROR_TYPE_ACTION,
> > > NULL,
> > > >  					  "can't have 2 flag"
> > > >  					  " actions in same flow");
> > > > +	if (attr->egress)
> > > > +		return rte_flow_error_set(error, ENOTSUP,
> > > > +
> > > RTE_FLOW_ERROR_TYPE_ATTR_EGRESS,
> > > > +					  NULL,
> > >
> > > These two lines could be one line.
> > Can't do, It exceeds the 80 characters limit.
> 
> 	if (attr->egress)
> 		return rte_flow_error_set(error, ENOTSUP,
> 
> RTE_FLOW_ERROR_TYPE_ATTR_EGRESS, NULL,
> 0123456789012345678901234567890123456789012345678901234567890123456
> 7890123456789
> 					  "flag action not supported for "
> 					  "egress");
> 
> Exactly 80 :-)

Done.

> 
> Thanks,
> Yongseok

  reply	other threads:[~2018-10-03 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 14:25 Dekel Peled
2018-09-29  9:24 ` Yongseok Koh
2018-10-03  6:06   ` Dekel Peled
2018-10-03  7:28     ` Yongseok Koh
2018-10-03 13:02       ` Dekel Peled [this message]
2018-10-07 14:01 ` [dpdk-dev] [PATCH v2] " Dekel Peled
2018-10-08 18:55   ` Yongseok Koh
2018-10-11  8:14     ` Shahaf Shuler

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=VI1PR05MB42240A6F053B7B59751F9181B6E90@VI1PR05MB4224.eurprd05.prod.outlook.com \
    --to=dekelp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=orika@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=yskoh@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 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).