Re: [Cake] Announce - possible new feature - DSCP cleaning

["Toke Høiland-Jørgensen" <toke@toke.dk>]

Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> writes:

> The jury hasn't even been assembled, let alone sat as to whether these
> (potentially) increasing targets/intervals on 'slow' links is a good
> thing(tm) or not.

I think I was leaning towards 'no' last time around on this.

>> memory used: 612600b of 15140Kb # not huge on parsing this
>> capacity estimate: 724522Kbit # not huge on parsing this
>
> That's a function of the sprint_size(), sprint_time(), sprint_rate()
> (and matching get_*() ) helpers provided by tc.  Similar 'playing with'
> units can be seen in the threshold values for each tin.  A 'classic'
> example demonstrating both A) and unit playing:

I think we should prioritise human readability in tc output. If we want
to have a mode that is easy to parse, make it a separate one (was
looking for a 'machine-readable' switch to tc, but there doesn't seem to
be one).

Would it be viable to get a patch into iproute that makes it sprout csv
or json, do you think?

Besides, as far as being a pain to parse, the 'tin table' is way worse,
as far as I'm concerned.

-Toke