From: Florian Fainelli <f.fainelli@gmail.com>
To: Ido Schimmel <idosch@mellanox.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: Tue, 8 Jan 2019 20:39:21 -0800 [thread overview]
Message-ID: <357c847d-1b74-20dc-383b-2f9119d66a41@gmail.com> (raw)
In-Reply-To: <20190104135837.GB11955@splinter>
Le 1/4/19 à 5:58 AM, Ido Schimmel a écrit :
> 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.
Yes, that's what I meant, that change is queued in my local branch right
now which will get submitted once net-next open backs again.
Thanks!
--
Florian
prev parent reply other threads:[~2019-01-09 4:39 UTC|newest]
Thread overview: 4+ 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 23:26 ` Randy Dunlap
2019-01-04 13:58 ` Ido Schimmel
2019-01-09 4:39 ` Florian Fainelli [this message]
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=357c847d-1b74-20dc-383b-2f9119d66a41@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=idosch@mellanox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox