diff options
author | Robert Shearman <rshearma@brocade.com> | 2017-01-16 14:16:36 +0000 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-01-17 14:38:43 -0500 |
commit | aefb4d4ad83b608cb8e0cab8d3cd8e57d3f91feb (patch) | |
tree | 2ccd7c1b81ae95848db32b29070c6be9c3a6e0de /.gitattributes | |
parent | 55f78fcdd88c6298933645b74c32ce3788bed7eb (diff) | |
download | op-kernel-dev-aefb4d4ad83b608cb8e0cab8d3cd8e57d3f91feb.zip op-kernel-dev-aefb4d4ad83b608cb8e0cab8d3cd8e57d3f91feb.tar.gz |
net: AF-specific RTM_GETSTATS attributes
Add the functionality for including address-family-specific per-link
stats in RTM_GETSTATS messages. This is done through adding a new
IFLA_STATS_AF_SPEC attribute under which address family attributes are
nested and then the AF-specific attributes can be further nested. This
follows the model of IFLA_AF_SPEC on RTM_*LINK messages and it has the
advantage of presenting an easily extended hierarchy. The rtnl_af_ops
structure is extended to provide AFs with the opportunity to fill and
provide the size of their stats attributes.
One alternative would have been to provide AFs with the ability to add
attributes directly into the RTM_GETSTATS message without a nested
hierarchy. I discounted this approach as it increases the rate at
which the 32 attribute number space is used up and it makes
implementation a little more tricky for stats dump resuming (at the
moment the order in which attributes are added to the message has to
match the numeric order of the attributes).
Another alternative would have been to register per-AF RTM_GETSTATS
handlers. I discounted this approach as I perceived a common use-case
to be getting all the stats for an interface and this approach would
necessitate multiple requests/dumps to retrieve them all.
Signed-off-by: Robert Shearman <rshearma@brocade.com>
Acked-by: Roopa Prabhu <roopa@cumulusnetworks.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to '.gitattributes')
0 files changed, 0 insertions, 0 deletions