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,
	nikolay@cumulusnetworks.com, dsa@cumulusnetworks.com,
	edumazet@google.com, willemb@google.com, johannes.berg@intel.com,
	dcaratti@redhat.com, pabeni@redhat.com, daniel@iogearbox.net,
	f.fainelli@gmail.com, fw@strlen.de, gfree.wind@vip.163.com
Subject: Re: [patch net-next 1/7] skbuff: Add the offload_mr_fwd_mark field
Date: Thu, 28 Sep 2017 19:49:03 +0200	[thread overview]
Message-ID: <20170928174903.GE14940@lunn.ch> (raw)
In-Reply-To: <20170928173415.15551-2-jiri@resnulli.us>

On Thu, Sep 28, 2017 at 07:34:09PM +0200, Jiri Pirko wrote:
> From: Yotam Gigi <yotamg@mellanox.com>
> 
> Similarly to the offload_fwd_mark field, the offload_mr_fwd_mark field is
> used to allow partial offloading of MFC multicast routes.

> The reason why the already existing "offload_fwd_mark" bit cannot be used
> is that a switchdev driver would want to make the distinction between a
> packet that has already gone through L2 forwarding but did not go through
> multicast forwarding, and a packet that has already gone through both L2
> and multicast forwarding.

Hi Jiri

So we are talking about l2 vs l3. So why not call this
offload_l3_fwd_mark?

Is there anything really specific to multicast here?

   Thanks
      Andrew

  reply	other threads:[~2017-09-28 17:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 17:34 [patch net-next 0/7] mlxsw: Add support for partial multicast route offload Jiri Pirko
2017-09-28 17:34 ` [patch net-next 1/7] skbuff: Add the offload_mr_fwd_mark field Jiri Pirko
2017-09-28 17:49   ` Andrew Lunn [this message]
2017-09-29  6:05     ` Jiri Pirko
2017-09-29 11:14   ` Davide Caratti
2017-09-29 11:36     ` Yuval Mintz
2017-09-28 17:34 ` [patch net-next 2/7] ipv4: ipmr: Add the parent ID field to VIF struct Jiri Pirko
2017-09-29  9:29   ` Nikolay Aleksandrov
2017-09-29  9:45     ` Nikolay Aleksandrov
2017-10-01  6:22       ` Yotam Gigi
2017-09-29  9:50   ` Nikolay Aleksandrov
2017-10-01  6:33     ` Yotam Gigi
2017-09-28 17:34 ` [patch net-next 3/7] ipv4: ipmr: Don't forward packets already forwarded by hardware Jiri Pirko
2017-09-28 17:56   ` Florian Fainelli
2017-10-01  8:51     ` Yotam Gigi
2017-09-28 17:34 ` [patch net-next 4/7] mlxsw: acl: Introduce ACL trap and forward action Jiri Pirko
2017-09-28 17:34 ` [patch net-next 5/7] mlxsw: spectrum: Add trap for multicast trap-and-forward routes Jiri Pirko
2017-09-28 17:34 ` [patch net-next 6/7] mlxsw: spectrum: mr_tcam: Add trap-and-forward multicast route Jiri Pirko
2017-09-28 17:34 ` [patch net-next 7/7] mlxsw: spectrum: mr: Support trap-and-forward routes 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=20170928174903.GE14940@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dcaratti@redhat.com \
    --cc=dsa@cumulusnetworks.com \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=fw@strlen.de \
    --cc=gfree.wind@vip.163.com \
    --cc=idosch@mellanox.com \
    --cc=jiri@resnulli.us \
    --cc=johannes.berg@intel.com \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.com \
    --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).