Re: [PATCH net-next 2/2] mpls: Packet stats

2017-01-16 Thread Robert Shearman
On 14/01/17 06:41, kbuild test robot wrote: Hi Robert, [auto build test ERROR on net-next/master] url:

Re: [PATCH net-next 2/2] mpls: Packet stats

2017-01-13 Thread kbuild test robot
Hi Robert, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/Robert-Shearman/net-AF-specific-RTM_GETSTATS-attributes/20170114-095819 config: i386-randconfig-sb0-01141243 (attached as .config) compiler: gcc-5 (Debian 5.4.1-2) 5.4.1 20160904 reproduce:

Re: [PATCH net-next 2/2] mpls: Packet stats

2017-01-13 Thread kbuild test robot
Hi Robert, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/Robert-Shearman/net-AF-specific-RTM_GETSTATS-attributes/20170114-095819 config: x86_64-randconfig-u0-01141334 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce:

Re: [PATCH net-next 2/2] mpls: Packet stats

2017-01-13 Thread Roopa Prabhu
On 1/13/17, 10:14 AM, Robert Shearman wrote: > Having MPLS packet stats is useful for observing network operation and > for diagnosing network problems. In the absence of anything better, > RFC2863 and RFC3813 are used for guidance for which stats to expose > and the semantics of them. In

[PATCH net-next 2/2] mpls: Packet stats

2017-01-13 Thread Robert Shearman
Having MPLS packet stats is useful for observing network operation and for diagnosing network problems. In the absence of anything better, RFC2863 and RFC3813 are used for guidance for which stats to expose and the semantics of them. In particular rx_noroutes maps to in unknown protos in RFC2863.