From: Dave Taht <dave.taht@gmail.com>
To: "Luis E. Garcia" <luis@bitamins.net>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] amd ryzen embedded nucs
Date: Tue, 20 Aug 2019 16:30:09 -0700 [thread overview]
Message-ID: <CAA93jw45S_XREAh+cU01JBoCNHQjkdLGk96Qgt-bAhqzUXiGyw@mail.gmail.com> (raw)
In-Reply-To: <CALnBQ5nHDZGhncQUANm=_5W8Xk3uKELfWFxBFT-otrpyBQ-mwA@mail.gmail.com>
On Tue, Aug 20, 2019 at 4:23 PM Luis E. Garcia <luis@bitamins.net> wrote:
>
> Dave,
> Have you upgraded the firmware on your apu2 boxes? The was a performance issue that was fixed a few weeks back.
"the firmware" - do you mean openwrt? or the bios? link?
I would be *delighted* to be able to shape inbound on those boxes to
nearly ~1gbit. On the other hand it would
run me out of motivation to try and make a quad core shaper work....
(not that I have a lot of motivation, since
it's been a year since I last tried, and it was pretty invasive....
I really liked the new "listification" work going on in mainline.
Still, my dream was to be rid of mirred entirely, and
to be able to do:
tc qdisc add dev eth0 ingress cake bandwidth X
or rather
tc qdisc add dev eth0 ingress mq bandwidth X
tc qdisc add dev eth0 ingress handle 1:1 cake
tc qdisc add dev eth0 ingress handle 1:2 cake
...
Which looked possible to fall out of that work (but haven't checked in a year)
> Regards,
> Luis
>
> On Tue, Aug 20, 2019 at 5:15 PM Dave Taht <dave.taht@gmail.com> wrote:
>>
>> since we run the apu2 out of cpu on inbound shaping, there are some
>> new ryzen boxes appearing. Here's one....
>>
>> https://www.amd.com/system/files/documents/R1000-product-brief.pdf
>>
>> http://asrock.pc.cdn.bitgravity.com/Download/e-catalog/iBOX-R1000.pdf
>>
>> I don't know why it uses realtek ethernet as the soc has 10Gbit
>> capable ethernet onboard.
>>
>> --
>>
>> Dave Täht
>> CTO, TekLibre, LLC
>> http://www.teklibre.com
>> Tel: 1-831-205-9740
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
next prev parent reply other threads:[~2019-08-20 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 23:14 Dave Taht
2019-08-20 23:22 ` Luis E. Garcia
2019-08-20 23:30 ` Dave Taht [this message]
2019-08-20 23:33 ` Luis E. Garcia
2019-08-21 0:52 ` Dave Taht
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw45S_XREAh+cU01JBoCNHQjkdLGk96Qgt-bAhqzUXiGyw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=luis@bitamins.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