Lets make wifi fast again!
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Pete Heist <pete@heistp.net>, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] NanoStation M5 anyone?
Date: Tue, 12 Jun 2018 12:24:13 +0200	[thread overview]
Message-ID: <87in6ojoaa.fsf@toke.dk> (raw)
In-Reply-To: <111C85D5-859A-4F2E-8D6E-DA32A4BD5AA8@heistp.net>

Pete Heist <pete@heistp.net> writes:

> This is an appeal to anyone who has access to a NanoStation M5 and a little time to try to reproduce this problem and add to this post:
>
> https://community.ubnt.com/t5/airMAX-Installation/NanoStation-M5-ping-spikes-about-once-per-second-even-just-to/td-p/2358704
>
> I’ve been trying unsuccessfully to demonstrate to Ubiquiti that they
> have a bug somewhere that causes isochronous latency spikes. It seems
> what’s happening is that for a fixed period of time (20ms when one
> Ethernet port is in use and 40ms when two are in use), once per
> second, the device queues packets until the pause is over. The
> function ar7240sw_phy_poll_reset in ag71xx_ar7240.c exactly describes
> the behavior of 20ms delays when one port is connected and 40ms delays
> when two ports are connected, so basically it appears that the
> Ethernet / internal switch device is being reset once per second for
> some reason.
>
> So far nobody has seemed to care (after all, who’s counting 40ms here
> or there when it comes to WiFi?), but it does pollute my test results
> and may be causing latency spikes wherever these devices are deployed
> (like, worldwide). So if anyone else tests this and can add some
> weight to the discussion, I’d be glad. :)

Does this only happen with stock firmware? I think I have reflashed all
of mine...

-Toke

  reply	other threads:[~2018-06-12 10:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12  7:46 Pete Heist
2018-06-12 10:24 ` Toke Høiland-Jørgensen [this message]
2018-06-12 11:00   ` Pete Heist
2018-06-12 12:09     ` Toke Høiland-Jørgensen
2018-06-12 15:09       ` Pete Heist
2018-06-12 15:52         ` Toke Høiland-Jørgensen
2018-06-12 16:12           ` Pete Heist

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/make-wifi-fast.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=87in6ojoaa.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=pete@heistp.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