Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "babel-users@lists.alioth.debian.org"
	<babel-users@lists.alioth.debian.org>,
	 make-wifi-fast@lists.bufferbloat.net,
	 "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] perverse powersave bug with sta/ap mode
Date: Tue, 26 Apr 2016 16:27:52 -0700	[thread overview]
Message-ID: <CALQXh-OOHwB4x7TDsmsYVfvuyA6Q_2Ay3EfVBENB6yNHN1HT_g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4v2J4yuNX8xeYwD5JGaeH3L_zYwZELrgNdZBtBco6WJQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 388 bytes --]

Has anyone modeled what the multicast to multiple-unicast efficiency
threshold is?  The point where you go from it being more efficient to send
multicast traffic to individual STAs instead of sending a monstrous (in
time) multicast-rate packet?

2, 5, 10 STAs?

The per-STA-queue work should make that relatively easy, by allowing the
packet to be dumped into each STA's queue...

-Aaron

[-- Attachment #2: Type: text/html, Size: 487 bytes --]

  reply	other threads:[~2016-04-26 23:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 23:18 Dave Taht
2016-04-26 23:27 ` Aaron Wood [this message]
2016-04-26 23:32   ` David Lang
2016-04-28 13:10   ` dpreed
2016-04-28 13:37     ` [Make-wifi-fast] [Babel-users] " Juliusz Chroboczek
2016-04-28 13:43       ` Toke Høiland-Jørgensen
2016-04-28 14:16         ` dpreed
2016-04-28 14:59           ` Juliusz Chroboczek
2016-04-28 15:44             ` Dave Taht
2016-04-28 16:09               ` Dave Taht
2016-04-28 17:10               ` [Make-wifi-fast] Multicast IHUs [was: perverse powersave bug with sta/ap mode] Juliusz Chroboczek
2016-04-28 17:46                 ` Dave Taht
2016-04-28 17:53                   ` [Make-wifi-fast] [Babel-users] " Henning Rogge
2016-04-28 18:46                   ` [Make-wifi-fast] Multicast IHUs Juliusz Chroboczek
2016-04-28 18:04                 ` [Make-wifi-fast] Multicast IHUs [was: perverse powersave bug with sta/ap mode] Dave Taht
2016-04-28 17:28               ` [Make-wifi-fast] Layering " Juliusz Chroboczek
2016-04-28 15:04         ` [Make-wifi-fast] [Cerowrt-devel] [Babel-users] perverse powersave bug with sta/ap mode moeller0
2016-04-28 16:05           ` [Make-wifi-fast] [Babel-users] [Cerowrt-devel] " Henning Rogge
2016-04-28 16:52             ` Dave Taht
2016-04-28 16:59               ` Henning Rogge
2016-04-28 18:54           ` [Make-wifi-fast] [Cerowrt-devel] [Babel-users] " Juliusz Chroboczek
2016-04-28 19:12             ` [Make-wifi-fast] [Babel-users] [Cerowrt-devel] " Henning Rogge
2016-04-28 19:29               ` Juliusz Chroboczek
2016-04-28 19:33                 ` Henning Rogge
2016-04-28 19:55                   ` Juliusz Chroboczek
2016-04-28 13:33   ` [Make-wifi-fast] [Babel-users] " Juliusz Chroboczek
2016-04-28 13:32 ` Juliusz Chroboczek
2016-05-12  0:28 ` [Make-wifi-fast] " Dave Taht

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=CALQXh-OOHwB4x7TDsmsYVfvuyA6Q_2Ay3EfVBENB6yNHN1HT_g@mail.gmail.com \
    --to=woody77@gmail.com \
    --cc=babel-users@lists.alioth.debian.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --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