On 05/29/2011 11:57 AM, Dave Taht wrote:
On Sun, May 29, 2011 at 9:21 AM, Juliusz Chroboczek
j...@pps.jussieu.fr mailto:j...@pps.jussieu.fr wrote:
And the irony is that the lower speed is specifically chosen for
multicast in order to make sure all clients in range can hear them
So after my experiments [1] yesterday with the wndr3700v2 hardware[2], I
came away
even more convinced that the wireless world and the wired worlds should
not be bridged together.
All the AQMs out there assume that it takes the same period of time to
deliver a packet consisting of X bytes to the
On 29 May, 2011, at 4:23 pm, Dave Taht wrote:
In my last 2 months of travel, I have seen multicast packets, such as ARP,
DHCP, MDNS, and now babel, all failing far, far, far more often than is
desirable. I have seen DHCP fail completely for hours at a time, I've seen
ARP take dozens of
On Sun, May 29, 2011 at 8:10 AM, Jonathan Morton chromati...@gmail.comwrote:
On 29 May, 2011, at 4:23 pm, Dave Taht wrote:
In my last 2 months of travel, I have seen multicast packets, such as
ARP, DHCP, MDNS, and now babel, all failing far, far, far more often than is
desirable. I have
And the irony is that the lower speed is specifically chosen for
multicast in order to make sure all clients in range can hear them
reliably.
It was my understanding that it was done for compatibility with older
devices, since 2 Mbit/s is the fastest rate supported by pre-B
spread-spectrum
Result - 130+Mbit performance on iperf on the lan (up from 60Mbit),
which is still pretty low
Are you seeing high CPU load in interrupt context? (Run top.)
-- Juliusz
___
Bloat mailing list
Bloat@lists.bufferbloat.net
Are you seeing high CPU load in interrupt context? (Run top.)
Yes. 99% sirq.
Could be due to a simplistic Ethernet driver. If you have the time and
energy, you may want to ask on dev.openwrt.org.
-- Juliusz
___
Bloat mailing list
On Sun, May 29, 2011 at 9:51 AM, Juliusz Chroboczek j...@pps.jussieu.frwrote:
Are you seeing high CPU load in interrupt context? (Run top.)
Yes. 99% sirq.
Could be due to a simplistic Ethernet driver. If you have the time and
energy, you may want to ask on dev.openwrt.org.
I will have
sorry, I meant to reply all.
Thanks for so quickly seeing the real cause of the upper limit.
On Sun, May 29, 2011 at 10:07 AM, Dave Taht dave.t...@gmail.com wrote:
On Sun, May 29, 2011 at 9:51 AM, Juliusz Chroboczek
j...@pps.jussieu.frwrote:
Are you seeing high CPU load in interrupt
Le dimanche 29 mai 2011 à 10:07 -0600, Dave Taht a écrit :
On Sun, May 29, 2011 at 9:51 AM, Juliusz Chroboczek
j...@pps.jussieu.fr wrote:
Are you seeing high CPU load in interrupt context? (Run
top.)
Yes. 99% sirq.
Could be
The datasheet has insufficient detail, and yet the switch seems enormously
capable, at least in theory. The kind of numbers under load I've seen thus
far (ranging from .9ms to 170ms) suggest port starvation.
http://realtek.info/pdf/rtl8366s_8366sr_datasheet_vpre-1.4_20071022.pdf
In looking
On Sun, May 29, 2011 at 10:33 AM, Eric Dumazet eric.duma...@gmail.comwrote:
Le dimanche 29 mai 2011 à 10:07 -0600, Dave Taht a écrit :
On Sun, May 29, 2011 at 9:51 AM, Juliusz Chroboczek
j...@pps.jussieu.fr wrote:
Are you seeing high CPU load in interrupt context? (Run
Le dimanche 29 mai 2011 à 11:02 -0600, Dave Taht a écrit :
The ethernet driver is the ag71xx driver as present in the wndr3700v2
(and mucho related atheros hardware). Regrettably so far as I can
tell, this one is out of tree, and is incorporated in the openwrt
build via a string
On Sun, May 29, 2011 at 11:17 AM, Eric Dumazet eric.duma...@gmail.comwrote:
Le dimanche 29 mai 2011 à 11:02 -0600, Dave Taht a écrit :
The kernel being used in capetown[1] is 2.6.37.6. - patched forward
from 2.6.39 for the pfifo ecn bug, the ipv6 ecn bug, and several other
bufferbloat
On 29 May, 2011, at 8:40 pm, Dave Taht wrote:
It is mildly early to point at the driver as being the issue - it could be
the switch or something else entirely. Would iptables or qos rules show up in
sirq?
I doubt it. I run some pretty old hardware sometimes, and I've never seen sirq
so
15 matches
Mail list logo
