Thread (109 messages) 109 messages, 6 authors, 2019-03-29

Re: [PATCH net-next v5 09/22] ethtool: implement EVENT notifications

From: Jiri Pirko <jiri@resnulli.us>
Date: 2019-03-27 13:04:39
Also in: lkml

Mon, Mar 25, 2019 at 06:08:21PM CET, mkubecek@suse.cz wrote:
Three types of netlink notifications are introduced:

 - ETHA_EVENT_NEWDEV to notify about newly registered network devices
 - ETHA_EVENT_DELDEV to notify about unregistered network devices
 - ETHA_EVENT_RENAMEDEV to notify about renamed network device

The notifications are triggered by NETDEV_REGISTER, NETDEV_UNREGISTER and
NETDEV_CHANGENAME notifiers.

These notifications are intended for applications and daemons monitoring
ethtool events to allow updating the list of existing devices without
having to open another socket for rtnetlink.
Wait. You duplicate events that are already going out through RTNETLINK.
App should open RTNETLINK in order to get those. Other apps are doing
that too. I don't think that duplications like this are desirable :/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help