From: David Ahern <dsa@cumulusnetworks.com>
To: netdev@vger.kernel.org
Cc: vyasevic@redhat.com, davem@davemloft.net,
David Ahern <dsa@cumulusnetworks.com>
Subject: [PATCH net-next 0/8] rtnetlink: Cleanup user notifications for netdev events
Date: Fri, 7 Apr 2017 14:25:32 -0700 [thread overview]
Message-ID: <1491600340-8359-1-git-send-email-dsa@cumulusnetworks.com> (raw)
Vlad's recent patch to add the event type to rtnetlink notifications
points out a number of redundant or unnecessary notifications sent to
userspace for events that are essentially internal to the kernel. Trim
the list before the new IFLA attributes become part of the UAPI.
David Ahern (8):
rtnetlink: Do not generate notifications for MTU events
rtnetlink: Do not generate notification for UDP_TUNNEL_PUSH_INFO
rtnetlink: Do not generate notifications for CHANGEADDR event
rtnetlink: Do not generate notifications for POST_TYPE_CHANGE event
rtnetlink: Remove NETDEV_CHANGEINFODATA netdev event
rtnetlink: Do not generate notifications for PRECHANGEUPPER event
rtnetlink: Do not generate notifications for NOTIFY_PEERS event
rtnetlink: Do not generate notifications for CHANGELOWERSTATE event
drivers/net/bonding/bond_options.c | 2 --
include/linux/netdevice.h | 1 -
include/uapi/linux/if_link.h | 9 ---------
net/core/rtnetlink.c | 36 ------------------------------------
4 files changed, 48 deletions(-)
--
2.1.4
next reply other threads:[~2017-04-07 21:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 21:25 David Ahern [this message]
2017-04-07 21:25 ` [PATCH net-next 1/8] rtnetlink: Do not generate notifications for MTU events David Ahern
2017-04-08 18:06 ` Roopa Prabhu
2017-04-08 18:13 ` David Ahern
2017-04-08 18:18 ` Roopa Prabhu
2017-04-10 15:39 ` Vlad Yasevich
2017-04-10 15:49 ` David Ahern
2017-04-15 1:51 ` Vlad Yasevich
2017-04-15 4:26 ` David Ahern
2017-04-18 7:52 ` Nicolas Dichtel
2017-04-09 1:36 ` Vlad Yasevich
2017-04-09 2:58 ` David Ahern
2017-04-07 21:25 ` [PATCH net-next 2/8] rtnetlink: Do not generate notification for UDP_TUNNEL_PUSH_INFO David Ahern
2017-04-07 21:25 ` [PATCH net-next 3/8] rtnetlink: Do not generate notifications for CHANGEADDR event David Ahern
2017-04-07 21:25 ` [PATCH net-next 4/8] rtnetlink: Do not generate notifications for POST_TYPE_CHANGE event David Ahern
2017-04-07 21:25 ` [PATCH net-next 5/8] rtnetlink: Remove NETDEV_CHANGEINFODATA netdev event David Ahern
2017-04-07 21:25 ` [PATCH net-next 6/8] rtnetlink: Do not generate notifications for PRECHANGEUPPER event David Ahern
2017-04-07 21:25 ` [PATCH net-next 7/8] rtnetlink: Do not generate notifications for NOTIFY_PEERS event David Ahern
2017-04-09 1:37 ` Vlad Yasevich
2017-04-07 21:25 ` [PATCH net-next 8/8] rtnetlink: Do not generate notifications for CHANGELOWERSTATE event David Ahern
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=1491600340-8359-1-git-send-email-dsa@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@redhat.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).