netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, yotamg@mellanox.com,
	idosch@mellanox.com, mlxsw@mellanox.com
Subject: Re: [patch net-next 07/12] mlxsw: spectrum: Add the multicast routing offloading logic
Date: Thu, 21 Sep 2017 17:26:54 +0200	[thread overview]
Message-ID: <20170921152654.GF27589@lunn.ch> (raw)
In-Reply-To: <20170921064338.1282-8-jiri@resnulli.us>

> +static void mlxsw_sp_mr_route_stats_update(struct mlxsw_sp *mlxsw_sp,
> +					   struct mlxsw_sp_mr_route *mr_route)
> +{
> +	struct mlxsw_sp_mr *mr = mlxsw_sp->mr;
> +	u64 packets, bytes;
> +
> +	if (mr_route->route_action == MLXSW_SP_MR_ROUTE_ACTION_TRAP)
> +		return;
> +
> +	mr->mr_ops->route_stats(mlxsw_sp, mr_route->route_priv, &packets,
> +				&bytes);
> +
> +	switch (mr_route->mr_table->proto) {
> +	case MLXSW_SP_L3_PROTO_IPV4:
> +		mr_route->mfc4->mfc_un.res.pkt = packets;
> +		mr_route->mfc4->mfc_un.res.bytes = bytes;

What about wrong_if and lastuse? 

Is an mfc with iif on the host, not the switch, not offloaded?

   Andrew

  reply	other threads:[~2017-09-21 15:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21  6:43 [patch net-next 00/12] mlxsw: Add support for offloading IPv4 multicast routes Jiri Pirko
2017-09-21  6:43 ` [patch net-next 01/12] fib: notifier: Add VIF add and delete event types Jiri Pirko
2017-09-21  6:43 ` [patch net-next 02/12] ipmr: Add reference count to MFC entries Jiri Pirko
2017-09-21 11:56   ` Nikolay Aleksandrov
2017-09-21  6:43 ` [patch net-next 03/12] ipmr: Add FIB notification access functions Jiri Pirko
2017-09-21 11:19   ` Nikolay Aleksandrov
2017-09-22  6:35     ` Yotam Gigi
2017-09-21  6:43 ` [patch net-next 04/12] ipmr: Send FIB notifications on MFC and VIF entries Jiri Pirko
2017-09-21 11:48   ` Nikolay Aleksandrov
2017-09-21  6:43 ` [patch net-next 05/12] net: ipmr: Add MFC offload indication Jiri Pirko
2017-09-21 11:27   ` Nikolay Aleksandrov
2017-09-21  6:43 ` [patch net-next 06/12] net: mroute: Check if rule is a default rule Jiri Pirko
2017-09-21  6:43 ` [patch net-next 07/12] mlxsw: spectrum: Add the multicast routing offloading logic Jiri Pirko
2017-09-21 15:26   ` Andrew Lunn [this message]
2017-09-22  8:36     ` Yotam Gigi
2017-09-22 13:21       ` Andrew Lunn
2017-09-23  9:32         ` Yotam Gigi
2017-09-23 14:41           ` Andrew Lunn
2017-09-21  6:43 ` [patch net-next 08/12] mlxsw: spectrum: Add the multicast routing hardware logic Jiri Pirko
2017-09-21  6:43 ` [patch net-next 09/12] mlxsw: spectrum: router: Squash the default route table to main Jiri Pirko
2017-09-21  6:43 ` [patch net-next 10/12] mlxsw: spectrum_router: Add multicast routes notification handling functionality Jiri Pirko
2017-09-21  6:43 ` [patch net-next 11/12] mlxsw: spectrum: Notify multicast router on RIF MTU changes Jiri Pirko
2017-09-21  6:43 ` [patch net-next 12/12] mlxsw: spectrum: router: Don't ignore IPMR notifications Jiri Pirko

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=20170921152654.GF27589@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=idosch@mellanox.com \
    --cc=jiri@resnulli.us \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=yotamg@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).