public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail•com>
To: Pablo Neira Ayuso <pablo@netfilter•org>
Cc: netdev@vger•kernel.org, davem@davemloft•net,
	thomas.lendacky@amd•com, f.fainelli@gmail•com,
	ariel.elior@cavium•com, michael.chan@broadcom•com,
	santosh@chelsio•com, madalin.bucur@nxp•com,
	yisen.zhuang@huawei•com, salil.mehta@huawei•com,
	jeffrey.t.kirsher@intel•com, tariqt@mellanox•com,
	saeedm@mellanox•com, jiri@mellanox•com, idosch@mellanox•com,
	jakub.kicinski@netronome•com, peppe.cavallaro@st•com,
	grygorii.strashko@ti•com, andrew@lunn•ch,
	vivien.didelot@savoirfairelinux•com, alexandre.torgue@st•com,
	joabreu@synopsys•com, linux-net-drivers@solarflare•com,
	ganeshgr@chelsio•com, ogerlitz@mellanox•com,
	Manish.Chopra@cavium•com
Subject: Re: [PATCH net-next,v3 12/12] qede: use ethtool_rx_flow_rule() to remove duplicated parser code
Date: Thu, 22 Nov 2018 14:59:08 -0200	[thread overview]
Message-ID: <20181122165908.GD8353@localhost.localdomain> (raw)
In-Reply-To: <20181121025132.14305-13-pablo@netfilter.org>

On Wed, Nov 21, 2018 at 03:51:32AM +0100, Pablo Neira Ayuso wrote:
...
>  static int
>  qede_parse_flower_attr(struct qede_dev *edev, __be16 proto,
> -		       struct tc_cls_flower_offload *f,
> -		       struct qede_arfs_tuple *tuple)
> +		       struct flow_rule *rule, struct qede_arfs_tuple *tuple)

What about s/qede_parse_flower_attr/qede_parse_flow_attr/ or so? As it
is not about flower anymore.

It also helps here:

> -static int qede_flow_spec_to_tuple(struct qede_dev *edev,
> -				   struct qede_arfs_tuple *t,
> -				   struct ethtool_rx_flow_spec *fs)
> +static int qede_flow_spec_to_rule(struct qede_dev *edev,
> +				  struct qede_arfs_tuple *t,
> +				  struct ethtool_rx_flow_spec *fs)
>  {
...
> +
> +	if (qede_parse_flower_attr(edev, proto, flow->rule, t)) {
> +		err = -EINVAL;
> +		goto err_out;
> +	}
> +
> +	/* Make sure location is valid and filter isn't already set */
> +	err = qede_flow_spec_validate(edev, &flow->rule->action, t,
> +				      fs->location);
...

  reply	other threads:[~2018-11-23  3:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21  2:51 [PATCH net-next,v3 00/12] add flow_rule infrastructure Pablo Neira Ayuso
2018-11-21  2:51 ` [PATCH net-next,v3 01/12] flow_dissector: add flow_rule and flow_match structures and use them Pablo Neira Ayuso
2018-11-21  2:51 ` [PATCH net-next,v3 02/12] net/mlx5e: support for two independent packet edit actions Pablo Neira Ayuso
2018-11-21  2:51 ` [PATCH net-next,v3 03/12] flow_dissector: add flow action infrastructure Pablo Neira Ayuso
2018-11-22  4:47   ` Florian Fainelli
2018-11-21  2:51 ` [PATCH net-next,v3 04/12] cls_api: add translator to flow_action representation Pablo Neira Ayuso
2018-11-21 21:15   ` Marcelo Ricardo Leitner
2018-11-21 23:48     ` Pablo Neira Ayuso
2018-11-22 16:33   ` Marcelo Ricardo Leitner
2018-11-21  2:51 ` [PATCH net-next,v3 05/12] cls_flower: add statistics retrieval infrastructure and use it Pablo Neira Ayuso
2018-11-21  2:51 ` [PATCH net-next,v3 06/12] drivers: net: use flow action infrastructure Pablo Neira Ayuso
2018-11-21  2:51 ` [PATCH net-next,v3 07/12] cls_flower: don't expose TC actions to drivers anymore Pablo Neira Ayuso
2018-11-21  2:51 ` [PATCH net-next,v3 08/12] flow_dissector: add wake-up-on-lan and queue to flow_action Pablo Neira Ayuso
2018-11-21  2:51 ` [PATCH net-next,v3 09/12] flow_dissector: add basic ethtool_rx_flow_spec to flow_rule structure translator Pablo Neira Ayuso
2018-11-22  4:57   ` Florian Fainelli
2018-11-22  6:19     ` Jiri Pirko
2018-11-22  4:59   ` Florian Fainelli
2018-11-22  6:21     ` Jiri Pirko
2018-11-21  2:51 ` [PATCH net-next,v3 10/12] dsa: bcm_sf2: use flow_rule infrastructure Pablo Neira Ayuso
2018-11-22  4:56   ` Florian Fainelli
2018-11-21  2:51 ` [PATCH net-next,v3 11/12] qede: place ethtool_rx_flow_spec after code after TC flower codebase Pablo Neira Ayuso
2018-11-21  2:51 ` [PATCH net-next,v3 12/12] qede: use ethtool_rx_flow_rule() to remove duplicated parser code Pablo Neira Ayuso
2018-11-22 16:59   ` Marcelo Ricardo Leitner [this message]
2018-11-22 16:22 ` [PATCH net-next,v3 00/12] add flow_rule infrastructure Marcelo Ricardo Leitner
2018-11-22 21:08   ` Marcelo Ricardo Leitner
2018-11-26 19:33     ` Pablo Neira Ayuso
2018-11-26 20:28       ` Marcelo Ricardo Leitner

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=20181122165908.GD8353@localhost.localdomain \
    --to=marcelo.leitner@gmail$(echo .)com \
    --cc=Manish.Chopra@cavium$(echo .)com \
    --cc=alexandre.torgue@st$(echo .)com \
    --cc=andrew@lunn$(echo .)ch \
    --cc=ariel.elior@cavium$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=f.fainelli@gmail$(echo .)com \
    --cc=ganeshgr@chelsio$(echo .)com \
    --cc=grygorii.strashko@ti$(echo .)com \
    --cc=idosch@mellanox$(echo .)com \
    --cc=jakub.kicinski@netronome$(echo .)com \
    --cc=jeffrey.t.kirsher@intel$(echo .)com \
    --cc=jiri@mellanox$(echo .)com \
    --cc=joabreu@synopsys$(echo .)com \
    --cc=linux-net-drivers@solarflare$(echo .)com \
    --cc=madalin.bucur@nxp$(echo .)com \
    --cc=michael.chan@broadcom$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=ogerlitz@mellanox$(echo .)com \
    --cc=pablo@netfilter$(echo .)org \
    --cc=peppe.cavallaro@st$(echo .)com \
    --cc=saeedm@mellanox$(echo .)com \
    --cc=salil.mehta@huawei$(echo .)com \
    --cc=santosh@chelsio$(echo .)com \
    --cc=tariqt@mellanox$(echo .)com \
    --cc=thomas.lendacky@amd$(echo .)com \
    --cc=vivien.didelot@savoirfairelinux$(echo .)com \
    --cc=yisen.zhuang@huawei$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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