[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57DEA9E2.3000703@cumulusnetworks.com>
Date: Sun, 18 Sep 2016 07:51:14 -0700
From: Roopa Prabhu <roopa@...ulusnetworks.com>
To: Patrick Ruddy <pruddy@...cade.com>
CC: netdev@...r.kernel.org, davem@...emloft.net, jiri@...nulli.us,
alexander.h.duyck@...el.com, stephen@...workplumber.org,
lboccass@...cade.com, sven@...cade.com
Subject: Re: [net-next PATCH] net: netlink messages for HW addr programming
On 9/15/16, 9:48 AM, Patrick Ruddy wrote:
> Add RTM_NEWADDR and RTM_DELADDR netlink messages with family
> AF_UNSPEC to indicate interest in specific unicast and multicast
> hardware addresses. These messages are sent when addresses are
> added or deleted from the appropriate interface driver.
> Added AF_UNSPEC GETADDR function to allow the netlink notifications
> to be replayed to avoid loss of state due to application start
> ordering or restart.
>
> Signed-off-by: Patrick Ruddy <pruddy@...cade.com>
> ---
RTM_NEWADDR and RTM_DELADDR are not used to add these entries to the kernel.
so, it seems a bit wrong to use RTM_NEWADDR and RTM_DELADDR to notify them to
userspace and also to request a special dump of these addresses.
This could just be a new nested netlink attribute in the existing link dump ?
Powered by blists - more mailing lists