From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] wifi implementation advice
Date: Mon, 17 May 2021 12:45:15 -0700 [thread overview]
Message-ID: <CAHb6Lvpo_7nr_XMvCXtvGo+CbH2dunp_9v1626_Qbzv5K=nP0A@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7NBsfbckcnA2wcXFwjAmD6zKRStY6CF4PmAhJ8a=se6A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1865 bytes --]
Thanks for sharing this.
The idea of getting rid of QOS seems interesting to me. Ironically, most
all the engineering is done around best effort logic paths so, in many
instances, one will find the BE outperforms VI per the tails of the latency
distributions.
I think the idea is "adaptive EDCAs." Some of the current values do change
per losing a TXOP but I think better generalizing the adaptations and
including things like AIFS could be more optimal.
Bob
On Mon, May 17, 2021 at 11:33 AM Dave Taht <dave.taht@gmail.com> wrote:
> I am reposting this link to the list because it has a ton of good
> implementation advice that a ton of people have been missing.
>
> https://blog.tohojo.dk/media/make-wifi-fast-qca.pdf
> --
> Latest Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
>
> Dave Täht CTO, TekLibre, LLC
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #1.2: Type: text/html, Size: 2649 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]
prev parent reply other threads:[~2021-05-17 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 18:33 Dave Taht
2021-05-17 19:45 ` Bob McMahon [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='CAHb6Lvpo_7nr_XMvCXtvGo+CbH2dunp_9v1626_Qbzv5K=nP0A@mail.gmail.com' \
--to=bob.mcmahon@broadcom.com \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.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