From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] [PATCH] killing retries harder, perhaps
Date: Fri, 3 Feb 2017 15:07:13 -0800 [thread overview]
Message-ID: <CAA93jw5F6a2LaQ4BNJG0Y9UOh8STOWXAh5Qcc3p0wwnRem8VGQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw57qqXFz2BMfqxMkE=OA=8RGdsT4R7ZFOf5xtDsg7Zz8w@mail.gmail.com>
And my aha! moment was that in the middle of the week, I'd turned off
wmm, which limits the rate set to the old style up to 58mbits.
My principal objective for the past week was to "make it crash", and
this is the longest the archer has ever survived intensive testing.
wmm on and off, multiple stations, 3 different distances, two to six
different clients, multicast rates set higher, ath9k and ath10k,
routed vs bridged (haven't returned to bridged), through the device,
to the device, channel scans, no channel scans, single queue vs
multi-queue, through sqm (with cake or fq_codel) and over the local
lan, ecn vs noecn, and I haven't got to blowing up multicast with
uftpd yet nor thc-ipv6.
Figuring out *why* things behaved badly was secondary, and kind of
hard, when they did. But no cases of RUD since jan 30.
thank ghu (and toke) for flent! And things are looking the most solid
they've ever been. As for whether this patch actually accomplished
anything or not...
tell you in 24 hours.
prev parent reply other threads:[~2017-02-03 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 23:47 Dave Taht
2017-02-03 0:37 ` Dave Taht
2017-02-03 13:21 ` Toke Høiland-Jørgensen
2017-02-03 19:30 ` Dave Taht
2017-02-03 23:07 ` Dave Taht [this message]
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=CAA93jw5F6a2LaQ4BNJG0Y9UOh8STOWXAh5Qcc3p0wwnRem8VGQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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