Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net
Subject: [Make-wifi-fast] Fwd: Re: berlin?
Date: Mon, 31 Aug 2015 03:58:48 -0700	[thread overview]
Message-ID: <CAA93jw5TPM=L-XF87rk_KOV1iqu-F49Z6pHfZ=3HadG8_i4C3Q@mail.gmail.com> (raw)
In-Reply-To: <3068870.XWUPjESX3M@prime>

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

---------- Forwarded message ----------
From: Simon Wunderlich <sw@simonwunderlich.de>
Date: Mon, Aug 31, 2015 at 3:09 AM
Subject: Re: Re: berlin?
To: Dave Taht <dave.taht@gmail.com>


Hi Dave,

hope you had a great trip so far! Here is that whitepaper I was talking about.
It is somewhat outdated already obviously, but maybe it will be interesting
(at least our test setup looks nice ;] ). We have created an ath9k patch to
account used txtime per station (including retries etc). The scheduling
function is then adapted to send to the station with the greatest airtime
deficit instead of just doing round robin. The missing communication between
the netdev layer and ath9k layer is also described here which made the concept
fail, but this could have been solved already with that new hook you
described.

Anyway, this research has been done for Open-Mesh but never got implemented in
a product so far. If there is interest and funds, I would be happy to continue
on that - I'm sure we can (re)use that patchset or our "wall of death" test
setup, I'll talk to Open-Mesh but they already did let me know earlier last
year that this would be possible.

Enjoy your trip,
    Simon

On Friday 21 August 2015 12:04:22 Dave Taht wrote:
> > BTW, I'm still trying to get the latest version of that fair airtime
> > analysis/summary we made, I'll send it to you as soon as I got it.
>
> TIA!
>
> > Cheers,
> >
> >     Simon
> >
> > On Friday 21 August 2015 09:24:48 Dave Taht wrote:
> >> I am heading to berlin on the 28th. Where are you based?


-- 
Dave Täht
endo is a terrible disease: http://www.gofundme.com/SummerVsEndo

[-- Attachment #2: Whitepaper-airtime fairness.pdf --]
[-- Type: application/pdf, Size: 914114 bytes --]

[-- Attachment #3: signature.asc --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

           reply	other threads:[~2015-08-31 10:58 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <3068870.XWUPjESX3M@prime>]

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='CAA93jw5TPM=L-XF87rk_KOV1iqu-F49Z6pHfZ=3HadG8_i4C3Q@mail.gmail.com' \
    --to=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