From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>, bridge@lists.linux-foundation.org
Cc: davem@davemloft.net,
Stephen Hemminger <stephen@networkplumber.org>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
nikolay@cumulusnetworks.com
Subject: [PATCHv2 net-next 0/6] bridge: support sending rntl info when we set attributes through sysfs/ioctl
Date: Tue, 5 Apr 2016 11:32:35 +0800 [thread overview]
Message-ID: <cover.1459827115.git.lucien.xin@gmail.com> (raw)
This patchset is used to support sending rntl info to user in some places,
and ensure that whenever those attributes change internally or from sysfs,
that a netlink notification is sent out to listeners.
It also make some adjustment in bridge sysfs so that we can implement this
easily.
I've done some tests on this patchset, like:
[br_sysfs]
1. change all the attribute values of br or brif:
$ echo $value > /sys/class/net/br0/bridge/{*}
$ echo $value > /sys/class/net/br0/brif/eth1/{*}
2. meanwhile, on another terminal to observe the msg:
$ bridge monitor
[br_ioctl]
1. in bridge-utils package, do some changes in br_set, let brctl command
use ioctl to set attribute:
if ((ret = set_sysfs(path, value)) < 0) { -->
if (1) {
$ brctl set*
2. meanwhile, on another terminal to observe the msg:
$ bridge monitor
This test covers all the attributes that brctl and sysfs support to set.
Xin Long (6):
bridge: simplify the flush_store by calling store_bridge_parm
bridge: simplify the forward_delay_store by calling store_bridge_parm
bridge: simplify the stp_state_store by calling store_bridge_parm
bridge: a netlink notification should be sent when those attributes
are changed by br_sysfs_br
bridge: a netlink notification should be sent when those attributes
are changed by br_sysfs_if
bridge: a netlink notification should be sent when those attributes
are changed by ioctl
net/bridge/br_ioctl.c | 40 +++++++++++++----------
net/bridge/br_sysfs_br.c | 83 +++++++++++++++++++-----------------------------
net/bridge/br_sysfs_if.c | 5 +--
net/bridge/br_vlan.c | 30 +++--------------
4 files changed, 65 insertions(+), 93 deletions(-)
--
2.1.0
next reply other threads:[~2016-04-05 3:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 3:32 Xin Long [this message]
2016-04-05 3:32 ` [PATCHv2 net-next 1/6] bridge: simplify the flush_store by calling store_bridge_parm Xin Long
2016-04-05 3:32 ` [PATCHv2 net-next 2/6] bridge: simplify the forward_delay_store " Xin Long
2016-04-05 3:32 ` [PATCHv2 net-next 3/6] bridge: simplify the stp_state_store " Xin Long
2016-04-05 3:32 ` [PATCHv2 net-next 4/6] bridge: a netlink notification should be sent when those attributes are changed by br_sysfs_br Xin Long
2016-04-05 3:32 ` [PATCHv2 net-next 5/6] bridge: a netlink notification should be sent when those attributes are changed by br_sysfs_if Xin Long
2016-04-05 3:32 ` [PATCHv2 net-next 6/6] bridge: a netlink notification should be sent when those attributes are changed by ioctl Xin Long
2016-04-05 5:08 ` [PATCHv2 net-next 3/6] bridge: simplify the stp_state_store by calling store_bridge_parm Toshiaki Makita
2016-04-06 20:10 ` David Miller
2016-04-07 3:49 ` Xin Long
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=cover.1459827115.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@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;
as well as URLs for NNTP newsgroup(s).