On Sun, Oct 16, 2016 at 9:22 AM, Ben Greear wrote:
>
>
> On 10/16/2016 08:30 AM, STR . wrote:
>>>
>>> BQL + fq_codel kills bufferbloat at line rate (10,100,1000mbit) on
>>> ethernet cards. It also works if you have hardware flow control on the the
>>> ethernet.
>>> It can't do anything on download
On Sun, Oct 16, 2016 at 9:22 AM, Ben Greear wrote:
>
>
> On 10/16/2016 08:30 AM, STR . wrote:
>>>
>>> BQL + fq_codel kills bufferbloat at line rate (10,100,1000mbit) on
>>> ethernet cards. It also works if you have hardware flow control on the the
>>> ethernet.
>>> It can't do anything on download
On 10/16/2016 05:30 PM, STR . wrote:
>> I'd rather like to see the bcp38 stuff a default, but although we made the
>> code work right for one layer of nat, too many people have more than that. :(
> Double NAT?
>
Common for fibre providers, and 3G/4G, where the "modem" isn't a modem
but a route
On 10/16/2016 08:30 AM, STR . wrote:
BQL + fq_codel kills bufferbloat at line rate (10,100,1000mbit) on ethernet
cards. It also works if you have hardware flow control on the the ethernet.
It can't do anything on downloads.
If your connection is not at line rate or the download is overbuffere
> BQL + fq_codel kills bufferbloat at line rate (10,100,1000mbit) on ethernet
> cards. It also works if you have hardware flow control on the the ethernet.
> It can't do anything on downloads.
> If your connection is not at line rate or the download is overbuffered
> (looks like 20Mbit here), yo
On Sun, Oct 16, 2016 at 4:37 AM, STR . wrote:
>>Everything important in CeroWrt long ago made it upstream - the apu2 (which,
>>btw, I have been using as my main test platform for the make-wifi-fast work)
>>has BQL on the intel network drivers
> Interesting, it didn't seem like it's implemented w
>Everything important in CeroWrt long ago made it upstream - the apu2 (which,
>btw, I have been using as my main test platform for the make-wifi-fast work)
>has BQL on the intel network drivers
Interesting, it didn't seem like it's implemented when I test as suggested by
https://www.bufferbloat.
Everything important in CeroWrt long ago made it upstream - the apu2
(which, btw, I have been using as my main test platform for the
make-wifi-fast work) has BQL on the intel network drivers, already,
fq_codel is the default in lede, sch_cake is available as an optional
package, and the make-wifo-f
On 10/16/2016 11:49 AM, STR . wrote:
> Could we also build 'lsusb' along with lspci? I'd recommend bundling the
> usb-serial-kmod too as a lot of mini-pci devices present themselves as USB.
Yes to this. Many 3G/4G modems on mini-pcie port are using usb lines of
mini-pcie port and not pcie lines
My 2c on USB, lm-sensors and the NCT chip on this board.
> This is an RFC to port the PC Engines APU2 board to LEDE. Currently this
is based on my unofficial repo at https://github.com/riptidewave93/LEDE-APU2
and after a discussion on the lede-dev IRC on the best plan of action, which
was to move
On 10/14/2016 10:19 AM, Chris Blake wrote:
This is an RFC to port the PC Engines APU2 board to LEDE. Currently this is
based on my unofficial repo at https://github.com/riptidewave93/LEDE-APU2 and
after a discussion on the lede-dev IRC on the best plan of action, which was to
move this device
Chris,
You might be interested in
https://lists.openwrt.org/pipermail/openwrt-devel/2015-February/031200.html,
which was never commited.
Regards,
---
Luiz Angelo Daros de Luca, Me.
luizl...@gmail.com
___
Lede-dev mailing list
Lede-dev
This is an RFC to port the PC Engines APU2 board to LEDE. Currently this is
based on my unofficial repo at https://github.com/riptidewave93/LEDE-APU2 and
after a discussion on the lede-dev IRC on the best plan of action, which was to
move this device to a profile under x86_64.
Things Working:
13 matches
Mail list logo
