From: Ido Schimmel <idosch@mellanox.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: "andrew@lunn.ch" <andrew@lunn.ch>,
"nikolay@cumulusnetworks.com" <nikolay@cumulusnetworks.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"roopa@cumulusnetworks.com" <roopa@cumulusnetworks.com>,
"bridge@lists.linux-foundation.org"
<bridge@lists.linux-foundation.org>,
"vivien.didelot@gmail.com" <vivien.didelot@gmail.com>,
Jiri Pirko <jiri@mellanox.com>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [Bridge] [PATCH net-next v2] Documentation: networking: Clarify switchdev devices behavior
Date: Fri, 4 Jan 2019 13:58:40 +0000 [thread overview]
Message-ID: <20190104135837.GB11955@splinter> (raw)
In-Reply-To: <20190103224702.21541-1-f.fainelli@gmail.com>
On Thu, Jan 03, 2019 at 02:47:02PM -0800, Florian Fainelli wrote:
> +A switchdev driver can also refuse to support dynamic toggling of the VLAN
> +filtering knob at runtime and require a destruction of the bridge device(s) and
> +a creation of new bridge device(s) with a different VLAN filtering value to
> +ensure VLAN awareness is pushed down to the HW.
...
> +Similarly to VLAN filtering, if dynamic toggling of the IGMP snooping
I think you meant to continue this sentence with something about vetoing
the operation. Note that it is not currently possible as
br_mc_disabled_update() returns void. Can be extended if needed.
> --
> 2.17.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Ido Schimmel <idosch@mellanox.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"andrew@lunn.ch" <andrew@lunn.ch>, Jiri Pirko <jiri@mellanox.com>,
"vivien.didelot@gmail.com" <vivien.didelot@gmail.com>,
"nikolay@cumulusnetworks.com" <nikolay@cumulusnetworks.com>,
"roopa@cumulusnetworks.com" <roopa@cumulusnetworks.com>,
"bridge@lists.linux-foundation.org"
<bridge@lists.linux-foundation.org>,
"cphealy@gmail.com" <cphealy@gmail.com>
Subject: Re: [PATCH net-next v2] Documentation: networking: Clarify switchdev devices behavior
Date: Fri, 4 Jan 2019 13:58:40 +0000 [thread overview]
Message-ID: <20190104135837.GB11955@splinter> (raw)
In-Reply-To: <20190103224702.21541-1-f.fainelli@gmail.com>
On Thu, Jan 03, 2019 at 02:47:02PM -0800, Florian Fainelli wrote:
> +A switchdev driver can also refuse to support dynamic toggling of the VLAN
> +filtering knob at runtime and require a destruction of the bridge device(s) and
> +a creation of new bridge device(s) with a different VLAN filtering value to
> +ensure VLAN awareness is pushed down to the HW.
...
> +Similarly to VLAN filtering, if dynamic toggling of the IGMP snooping
I think you meant to continue this sentence with something about vetoing
the operation. Note that it is not currently possible as
br_mc_disabled_update() returns void. Can be extended if needed.
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-01-04 13:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 22:47 [Bridge] [PATCH net-next v2] Documentation: networking: Clarify switchdev devices behavior Florian Fainelli
2019-01-03 22:47 ` Florian Fainelli
2019-01-03 23:26 ` [Bridge] " Randy Dunlap
2019-01-03 23:26 ` Randy Dunlap
2019-01-04 13:58 ` Ido Schimmel [this message]
2019-01-04 13:58 ` Ido Schimmel
2019-01-09 4:39 ` [Bridge] " Florian Fainelli
2019-01-09 4:39 ` Florian Fainelli
2019-01-09 4:39 ` Florian Fainelli
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=20190104135837.GB11955@splinter \
--to=idosch@mellanox.com \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=vivien.didelot@gmail.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.