From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
bridge@lists.linux-foundation.org, mrv@mojatatu.com,
dsa@cumulusnetworks.com, davem@davemloft.net
Subject: Re: [PATCH net-next v3 1/2] bridge: netlink: make setlink/dellink notifications more accurate
Date: Thu, 26 Oct 2017 11:25:21 +0300 [thread overview]
Message-ID: <3a9ba7b5-802c-7907-b91d-be076d448e78@cumulusnetworks.com> (raw)
In-Reply-To: <20171026101702.6ff21fc1@shemminger-XPS-13-9360>
On 26/10/17 11:17, Stephen Hemminger wrote:
> On Thu, 26 Oct 2017 00:59:41 +0300
> Nikolay Aleksandrov <nikolay@cumulusnetworks.com> wrote:
>
>> Before this patch we had cases that either sent notifications when there
>> were in fact no changes (e.g. non-existent vlan delete) or didn't send
>> notifications when there were changes (e.g. vlan add range with an error in
>> the middle, port flags change + vlan update error). This patch sends down
>> a boolean to the functions setlink/dellink use and if there is even a
>> single configuration change (port flag, vlan add/del, port state) then
>> we always send a notification. This is all done to keep backwards
>> compatibility with the opportunistic vlan delete, where one could
>> specify a vlan range that has missing vlans inside and still everything
>> in that range will be cleared, this is mostly used to clear the whole
>> vlan config with a single call, i.e. range 1-4094.
>>
>> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
>
> This looks correct.
> As a general note, generating a notice with no change should be ok for a correctly
> written application. But missing a notification would cause synchronization problems.
>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
>
Stephen, thank you for the review. Could you please send the ack to
v4 of this set ? Since it's already sent, I can't add it myself.
Thanks,
Nik
next prev parent reply other threads:[~2017-10-26 8:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 12:32 [PATCH net-next v2 0/2] bridge: make setlink/dellink notifications more accurate Nikolay Aleksandrov
2017-10-24 12:32 ` [PATCH net-next v2 1/2] bridge: netlink: " Nikolay Aleksandrov
2017-10-24 12:32 ` [PATCH net-next v2 2/2] bridge: vlan: signal if anything changed on vlan add Nikolay Aleksandrov
2017-10-25 20:51 ` kbuild test robot
2017-10-25 21:49 ` [PATCH net-next v2 0/2] bridge: make setlink/dellink notifications more accurate Nikolay Aleksandrov
2017-10-25 21:59 ` [PATCH net-next v3 " Nikolay Aleksandrov
2017-10-25 21:59 ` [PATCH net-next v3 1/2] bridge: netlink: " Nikolay Aleksandrov
2017-10-26 8:17 ` Stephen Hemminger
2017-10-26 8:25 ` Nikolay Aleksandrov [this message]
2017-10-25 21:59 ` [PATCH net-next v3 2/2] bridge: vlan: signal if anything changed on vlan add Nikolay Aleksandrov
2017-10-25 22:14 ` [PATCH net-next v3 0/2] bridge: make setlink/dellink notifications more accurate Nikolay Aleksandrov
2017-10-25 22:52 ` [PATCH net-next v4 " Nikolay Aleksandrov
2017-10-25 22:52 ` [PATCH net-next v4 1/2] bridge: netlink: " Nikolay Aleksandrov
2017-10-25 22:52 ` [PATCH net-next v4 2/2] bridge: vlan: signal if anything changed on vlan add Nikolay Aleksandrov
2017-10-26 10:16 ` Toshiaki Makita
2017-10-26 11:02 ` [Bridge] " Nikolay Aleksandrov
2017-10-26 11:08 ` Nikolay Aleksandrov
2017-10-26 1:12 ` [PATCH net-next v3 0/2] bridge: make setlink/dellink notifications more accurate David Miller
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=3a9ba7b5-802c-7907-b91d-be076d448e78@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=mrv@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=stephen@networkplumber.org \
/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