Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Pete Heist <pete@eventide.io>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Testing wanted: Statistics API rework
Date: Wed, 25 Apr 2018 18:53:06 +0200	[thread overview]
Message-ID: <87wowv5itp.fsf@toke.dk> (raw)
In-Reply-To: <F8727D85-78A6-4B8C-966D-9BF6671A09C3@eventide.io>

Pete Heist <pete@eventide.io> writes:

>> On Apr 25, 2018, at 11:15 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>> 
>> Pete Heist <pete@eventide.io> writes:
>> 
>>> I requested a re-build over in the Ubiquiti EdgeOS forums. Between
>>> ER-X and ER-L I think that would cover 32-bit mips (little endian) and
>>> 64-bit mips (big endian). Anything specific to test besides “it
>>> works"? :)
>> 
>> We need to verify that it will still print statistics and that the
>> values do not look weird (especially the per-tin 'bytes' counter since
>> that is a 64bit value).
>
>
> In case you didn’t see it before, Lochnair has automatic builds set up
> (cool) for EdgeOS that are failing as of yesterday:
>
> https://build.lochnair.net/job/ubiquiti/job/bufferbloat/job/cake_cobalt/
>
> It may very well be due to the 3.10(!) kernel it ships with, but in
> case it helps somehow, go to the latest build and “Console Output”. In
> case you commit a change, the git repo is polled once an hour,
> apparently. Otherwise, I don’t have an easy way to test mips…

Yup, definitely an issue with kernel versions. Guess we'll have to go
back and add in compatibility stuff later.

Kevin was nice enough to test on an Archer C7, so I think we are good
for now :)

-Toke


      reply	other threads:[~2018-04-25 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 21:30 Toke Høiland-Jørgensen
2018-04-25  0:39 ` Marcelo Ricardo Leitner
2018-04-25  5:33 ` Pete Heist
2018-04-25  9:15   ` Toke Høiland-Jørgensen
2018-04-25 16:28     ` Pete Heist
2018-04-25 16:53       ` Toke Høiland-Jørgensen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wowv5itp.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cake@lists.bufferbloat.net \
    --cc=pete@eventide.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox