From: Nikolay Aleksandrov <niko...@cumulusnetworks.com>
Date: Thu, 14 Jul 2016 19:28:27 +0300

> In preparation for hardware offloading of ipmr/ip6mr we need an
> interface that allows to check (and later update) the age of entries.
> Relying on stats alone can show activity but not actual age of the entry,
> furthermore when there're tens of thousands of entries a lot of the
> hardware implementations only support "hit" bits which are cleared on
> read to denote that the entry was active and shouldn't be aged out,
> these can then be naturally translated into age timestamp and will be
> compatible with the software forwarding age. Using a lastuse entry doesn't
> affect performance because the members in that cache line are written to
> along with the age.
> Since all new users are encouraged to use ipmr via netlink, this is
> exported via the RTA_EXPIRES attribute.
> Also do a minor local variable declaration style adjustment - arrange them
> longest to shortest.
> 
> Signed-off-by: Nikolay Aleksandrov <niko...@cumulusnetworks.com>
> CC: Roopa Prabhu <ro...@cumulusnetworks.com>
> CC: Shrijeet Mukherjee <s...@cumulusnetworks.com>
> CC: Satish Ashok <sas...@cumulusnetworks.com>
> CC: Donald Sharp <sha...@cumulusnetworks.com>
> CC: David S. Miller <da...@davemloft.net>
> CC: Alexey Kuznetsov <kuz...@ms2.inr.ac.ru>
> CC: James Morris <jmor...@namei.org>
> CC: Hideaki YOSHIFUJI <yoshf...@linux-ipv6.org>
> CC: Patrick McHardy <ka...@trash.net>
> ---
> v2: Just reuse RTA_EXPIRES instead to minimize the attr size and simplify,
> others will be added when needed

Applied, thanks.

Reply via email to