From: Roopa Prabhu <roopa@cumulusnetworks.com>
To: Patrick Ruddy <pruddy@brocade.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, jiri@resnulli.us,
alexander.h.duyck@intel.com, stephen@networkplumber.org,
lboccass@brocade.com, sven@brocade.com
Subject: Re: [net-next PATCH] net: netlink messages for HW addr programming
Date: Sun, 18 Sep 2016 07:51:14 -0700 [thread overview]
Message-ID: <57DEA9E2.3000703@cumulusnetworks.com> (raw)
In-Reply-To: <1473958082-30982-1-git-send-email-pruddy@brocade.com>
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@brocade.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 ?
next prev parent reply other threads:[~2016-09-18 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 16:48 [net-next PATCH] net: netlink messages for HW addr programming Patrick Ruddy
2016-09-18 14:51 ` Roopa Prabhu [this message]
2016-09-19 14:46 ` Patrick Ruddy
2016-09-20 5:31 ` Roopa Prabhu
2016-09-20 5:49 ` Jiri Pirko
2016-09-20 6:36 ` Roopa Prabhu
2016-10-03 10:42 ` Patrick Ruddy
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=57DEA9E2.3000703@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=lboccass@brocade.com \
--cc=netdev@vger.kernel.org \
--cc=pruddy@brocade.com \
--cc=stephen@networkplumber.org \
--cc=sven@brocade.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.