[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170620.152244.1055779320531168153.davem@davemloft.net>
Date: Tue, 20 Jun 2017 15:22:44 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: julien@...sta.com
Cc: nikolay@...ulusnetworks.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, sharpd@...ulusnetworks.com,
nicolas.dichtel@...nd.com
Subject: Re: [PATCH net-next v2 0/4] ipmr/ip6mr: add Netlink notifications
on cache reports
From: Julien Gomes <julien@...sta.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.
Powered by blists - more mailing lists