[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f05c6d50-ff95-6057-b2e5-bcc0c447b0c8@gmail.com>
Date: Sat, 27 May 2017 15:41:28 -0600
From: David Ahern <dsahern@...il.com>
To: Vladislav Yasevich <vyasevich@...il.com>, netdev@...r.kernel.org
Cc: roopa@...ulusnetworks.com, jiri@...nulli.us, vfalico@...il.com,
andy@...yhouse.net, Vladislav Yasevich <vyasevic@...hat.com>
Subject: Re: [PATCH V6 net-next 1/2] rtnl: Add support for netdev event to
link messages
On 5/27/17 8:14 AM, Vladislav Yasevich wrote:
> When netdev events happen, a rtnetlink_event() handler will send
> messages for every event in it's white list. These messages contain
> current information about a particular device, but they do not include
> the iformation about which event just happened. So, it is impossible
> to tell what just happend for these events.
>
> This patch adds a new extension to RTM_NEWLINK message called IFLA_EVENT
> that would have an encoding of event that triggered this
> message. This would allow the the message consumer to easily determine
> if it needs to perform certain actions.
>
> Signed-off-by: Vladislav Yasevich <vyasevic@...hat.com>
> ---
> include/linux/rtnetlink.h | 3 +-
> include/uapi/linux/if_link.h | 11 ++++++++
> net/core/dev.c | 2 +-
> net/core/rtnetlink.c | 65 ++++++++++++++++++++++++++++++++++++++------
> 4 files changed, 70 insertions(+), 11 deletions(-)
Acked-by: David Ahern <dsahern@...il.com>
Powered by blists - more mailing lists