Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: leetminiwheat <LeetMiniWheat@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	cake@lists.bufferbloat.net
Subject: [Cake] Current status and recommendations for APU2C*/ArcherC7 and ath10k platforms?
Date: Thu, 30 Mar 2017 00:08:59 -0400	[thread overview]
Message-ID: <CAGHZhqHfVsQGgqT7sEsqesf4j7mo5MUoDN_L1MY-Aat0QNWuxA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2478 bytes --]

Apologies I haven't had time to follow recent developments but are there
 any recent bufferbloat/CAKE related news/recommendations for the APU2
platform? Specifically the APU2C (previous was marvell I believe)

Hardware:
APU2C4 (AMD x86_64 | 4GB | 3x i210-AT)
WLE600VX (ath10k)
64GB mSATA

Also have an Archer C7 V2 (ath10k) and a old WDR3800 (ath9k) still
chugging along.

Looking for an optimal Archer C7 build or recommendations if anyone
has any experience on it.

Use case:
linespeed: 105/120 fiber -> APU2C4 primary gateway (and some WiFi) ->
Archer C7 & WNDR3800 for internal & guest networks
(undecided which of the last two for each task). My plan is to use
separate networks for bulk traffic others for latency sensitive stuff.

Anyways I searched through mailing lists and google but thought this
might be the best place(s) to ask.
I noticed dtaht is (or was) using an APU2 (though not sure which version
 of it since one of his posts refers to mvneta, the marvell platform).
Also saw that Dave's tc-adv didn't make it upstream?


From what I gathered, I found these relevant but perhaps outdated:

http://blog.cerowrt.org/post/birthday_problem/
<http://blog.cerowrt.org/post/birthday_problem/>
(refers to APU2 and it's 4 hardware queues but was this marvell/mvneta?)

https://github.com/riptidewave93/LEDE-APU2
(Older github repo for APU2 LEDE support but seems upstream now?)

https://github.com/Gr4ffy/LEDE-APU2
(older fork from above riptidewave93 LEDE-APU2)

https://github.com/greearb/lede-source-ct
(ath10k related; LEDE fork from Candela in which they apparently
obtained the ath10k firmware source code NDA)

https://github.com/dtaht/sch_cake/issues/46
(Fairness issue and a reference to dthat's custom tc not going upstream)

[multiple mailing list links]
(References to airtime-fairness? is  this primarily for ath9k?)

[APU2 ubuntu repo link I lost]
Saw a repo for dtaht's ubuntu build for APU2 somewhere?!? Or was it
under another name? If anyone knows the URL I'd love to borrow some
of the settings for testing.

https://github.com/pcengines/coreboot
https://github.com/pcengines/seabios
(APU2 related, they seem to still update their bios but they don't
release much.
I also saw some commits referring to ECC support on APU3, I guess ECC on
 the APU2 is a lost cause)


Any other more appropriate lists or IRC channels I might inquire in would
also
 be helpful.


P.S. My condolences for the loss of your lab @ Dave, that truly is a
travesty.

Thanks

[-- Attachment #2: Type: text/html, Size: 3702 bytes --]

             reply	other threads:[~2017-03-30  4:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30  4:08 leetminiwheat [this message]
2017-03-30  8:11 ` Toke Høiland-Jørgensen

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=CAGHZhqHfVsQGgqT7sEsqesf4j7mo5MUoDN_L1MY-Aat0QNWuxA@mail.gmail.com \
    --to=leetminiwheat@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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