From: David Miller <davem@davemloft.net>
To: julien@arista.com
Cc: nikolay@cumulusnetworks.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, sharpd@cumulusnetworks.com,
nicolas.dichtel@6wind.com
Subject: Re: [PATCH net-next v2 0/4] ipmr/ip6mr: add Netlink notifications on cache reports
Date: Tue, 20 Jun 2017 15:22:44 -0400 (EDT) [thread overview]
Message-ID: <20170620.152244.1055779320531168153.davem@davemloft.net> (raw)
In-Reply-To: <20170619204417.13230-1-julien@arista.com>
From: Julien Gomes <julien@arista.com>
Date: Mon, 19 Jun 2017 13:44:13 -0700
> Currently, all ipmr/ip6mr cache reports are sent through the
> mroute/mroute6 socket only.
> This forces the use of a single socket for mroute programming, cache
> reports and, regarding ipmr, IGMP messages without Router Alert option
> reception.
>
> The present patches are aiming to send Netlink notifications in addition
> to the existing igmpmsg/mrt6msg to give user programs a way to handle
> cache reports in parallel with multiple sockets other than the
> mroute/mroute6 socket.
>
> Changes in v2:
> - Changed attributes naming from {IPMRA,IP6MRA}_CACHEREPORTA_* to
> {IPMRA,IP6MRA}_CREPORT_*
> - Improved packet data copy to handle non-linear packets in
> ipmr/ip6mr cache report Netlink notification creation
> - Added two rtnetlink groups with restricted-binding
> - Changed cache report notified groups from RTNL_{IPV4,IPV6}_MROUTE to
> the new restricted groups in ipmr/ip6mr
Please address Nikolay's feedback about interface number limits etc.
Thanks.
prev parent reply other threads:[~2017-06-20 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 20:44 [PATCH net-next v2 0/4] ipmr/ip6mr: add Netlink notifications on cache reports Julien Gomes
2017-06-19 20:44 ` [PATCH net-next v2 1/4] rtnetlink: add NEWCACHEREPORT message type Julien Gomes
2017-06-20 8:54 ` Nikolay Aleksandrov
2017-06-19 20:44 ` [PATCH net-next v2 2/4] rtnetlink: add restricted rtnl groups for ipv4 and ipv6 mroute Julien Gomes
2017-06-20 8:56 ` Nikolay Aleksandrov
2017-06-19 20:44 ` [PATCH net-next v2 3/4] ipmr: add netlink notifications on igmpmsg cache reports Julien Gomes
2017-06-20 9:33 ` Nikolay Aleksandrov
2017-06-19 20:44 ` [PATCH net-next v2 4/4] ip6mr: add netlink notifications on mrt6msg " Julien Gomes
2017-06-20 9:37 ` Nikolay Aleksandrov
2017-06-20 19:22 ` David Miller [this message]
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=20170620.152244.1055779320531168153.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=julien@arista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=nikolay@cumulusnetworks.com \
--cc=sharpd@cumulusnetworks.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 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).