netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsa@cumulusnetworks.com>
To: netdev@vger.kernel.org
Cc: David Ahern <dsa@cumulusnetworks.com>
Subject: [PATCH net-next v2 0/8] rtnetlink: Cleanup user notifications for netdev events
Date: Tue, 11 Apr 2017 17:02:39 -0700	[thread overview]
Message-ID: <1491955367-12443-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 to put a dent in the notification storm.

v2
- rebased to top of net-next with IFLA_EVENT patch reverted
- dropped removal NETDEV_CHANGEINFODATA since it is intentionally
  only to send a message to userspace
- dropped NOTIFY_PEERS since Vlad's says it is needed for macvlans
- add patches to remove NETDEV_CHANGEUPPER and NETDEV_CHANGE_TX_QUEUE_LEN
  from the event list

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: Do not generate notifications for PRECHANGEUPPER event
  rtnetlink: Do not generate notifications for CHANGELOWERSTATE event
  rtnetlink: Do not generate notifications for NETDEV_CHANGEUPPER event
  rtnetlink: Do not generate notifications for
    NETDEV_CHANGE_TX_QUEUE_LEN event

 net/core/rtnetlink.c | 9 ---------
 1 file changed, 9 deletions(-)

-- 
2.1.4

             reply	other threads:[~2017-04-12  0:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12  0:02 David Ahern [this message]
2017-04-12  0:02 ` [PATCH net-next v2 1/8] rtnetlink: Do not generate notifications for MTU events David Ahern
2017-04-12  0:02 ` [PATCH net-next v2 2/8] rtnetlink: Do not generate notification for UDP_TUNNEL_PUSH_INFO David Ahern
2017-04-12  0:02 ` [PATCH net-next v2 3/8] rtnetlink: Do not generate notifications for CHANGEADDR event David Ahern
2017-04-12  0:02 ` [PATCH net-next v2 4/8] rtnetlink: Do not generate notifications for POST_TYPE_CHANGE event David Ahern
2017-04-12  0:02 ` [PATCH net-next v2 5/8] rtnetlink: Do not generate notifications for PRECHANGEUPPER event David Ahern
2017-04-12  0:02 ` [PATCH net-next v2 6/8] rtnetlink: Do not generate notifications for CHANGELOWERSTATE event David Ahern
2017-04-12  0:02 ` [PATCH net-next v2 7/8] rtnetlink: Do not generate notifications for NETDEV_CHANGEUPPER event David Ahern
2017-04-12  0:02 ` [PATCH net-next v2 8/8] rtnetlink: Do not generate notifications for NETDEV_CHANGE_TX_QUEUE_LEN event David Ahern
2017-04-13 17:17 ` [PATCH net-next v2 0/8] rtnetlink: Cleanup user notifications for netdev events 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=1491955367-12443-1-git-send-email-dsa@cumulusnetworks.com \
    --to=dsa@cumulusnetworks.com \
    --cc=netdev@vger.kernel.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).