> On 2 Jul 2018, at 12:38, Pete Heist <pete@heistp.net> wrote:
> 
> 
>> On Jul 2, 2018, at 12:19 PM, Pete Heist <pete@heistp.net> wrote:
>> 
>> What is TCA_STATS2 vs TCA_STATS and where does it come from? That’s at least one rtattr that’s null in print_qdisc on MIPS for some reason. That’s where I’m at, anyway…
> 
> I should have written that the rtattr at TCP_STATS2 has a zero len and type in it, not that it’s null.
> 
> But, um, I find it curious that tb[TCA_PAD] has valid looking values in it, and if I just go:
> 
> tb[TCA_STATS2] = tb[TCA_PAD]
> 
> right after parse_rtattr is called, I start getting tin stats printed that look valid. There should be zeroes or invalid values at tb[TCA_PAD], as that’s just supposed to be padding, right?
> 

Thank you Pete for your persistence in this.  I’m afraid I’ve just be zapped by a migraine so will be out of it for a day or two.

My understanding is the padding is only used align 64 bit values, if required… and we’re back to CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS

Sorry struggling to type english…which this may not be, can’t see clearly