Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Alan Jenkins <alan.christopher.jenkins@gmail.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
	cerowrt-devel@lists.bufferbloat.net,
	make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] Fwd: [tsvwg] Comments on draft-szigeti-tsvwg-ieee-802-11e
Date: Fri, 24 Jul 2015 12:38:45 +0200	[thread overview]
Message-ID: <A1CDC33B-5ABA-49D0-906B-13026C6395C1@gmx.de> (raw)
In-Reply-To: <55B09C76.20907@gmail.com>

Oh, boy,


On Jul 23, 2015, at 09:49 , Alan Jenkins <alan.christopher.jenkins@gmail.com> wrote:

> On 23/07/15 08:44, Jonathan Morton wrote:
>> 
>> Link to the spec?
>> 
>> - Jonathan Morton
>> 
>> 
> 
> https://datatracker.ietf.org/doc/draft-szigeti-tsvwg-ieee-802-11e/


	Not that I am a domain expert, but the whole web of slightly different versions of the same madness are quite amusing ;) What seems clear to me is that the wealth of 64 possible combinations looks a lot like a slippery slope (or better like a full blown slip and slide). 
	As far as I can see, hardware folks and MPLS opted for 3 bits maximum (I take it that wifi is actually 2 bits only), so what real use is in schemes using more than 8 different states beyond that mapping 12/16/64 to 8 is a fun exercise in bike-shedding… 

But since bike shedding is fun here is my “I am not even confused by partial knowledge” proposal for a 3+1bit marking scheme:

1) take the most significant 3 bits to deduce the CS equivalent (willfully ignoring the lower 3 bits) which will be treated as priority levels
2) decide were in the 3 bit range the “normal should be”, say 3 for example (to allow simplistic mapping to 2bit patterns)
3) extend by 1 bit at the end to get to 4 bits (I guess that would be shift by 1 bit?)
4) remark/remap the CS0 equivalent as “normal” + 1 (alternatively remap CS0 to “normal” and the CS that used to live there to “normal”+1)

Heck even just staying at 3 bits and just remarking CS0 to CS3 should do the trick, of putting in a lower priority class below the default best-effort traffic and still keep 802.11 mappings semi-working

And then just treat these as 8 different priority levels with the number coding the priority order using Jonathan’s approach of pairing higher priorities with lower guaranteed bandwidths allotments.
Blissfully ignore the proposed differentiation of the lower 3 bits until there is proof that they are actually helpful...


	I really wonder what the whole brouhaha is all about; wikipedia tells me ( https://en.wikipedia.org/wiki/IEEE_802.11e-2005 ) that Enhanced distributed channel access (EDCA) is sort of a best effort QoS system (what?) and that HCF Controlled Channel Access (HCCA) is where things should be going. Because then the AP manages all air time and all stations and the AP can do “normal”/high level priority queueing into the wifi adapters best-effort queue without the need for the “crazy" that is implementing media access as a race (especially with many clients that just does not sound like an efficient approach). But then I do not claim to be an expert in these matters.

Best Regards & sorry for the gantlet above
	Sebastian

> 
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast


  reply	other threads:[~2015-07-24 10:38 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E9C29602-7F1D-43AD-980C-050B58FA0AC6@iii.ca>
2015-07-23  6:48 ` [Cerowrt-devel] " Dave Taht
2015-07-23  7:44   ` Jonathan Morton
2015-07-23  7:49     ` Alan Jenkins
2015-07-24 10:38       ` Sebastian Moeller [this message]
2015-07-30 20:29   ` [Cerowrt-devel] " Jonathan Morton
2015-07-30 21:35     ` [Cerowrt-devel] [Make-wifi-fast] " Sebastian Moeller
2015-07-30 21:56       ` Jonathan Morton
2015-07-31  3:27         ` Sebastian Moeller
2015-07-31 16:47           ` dpreed
2015-07-31 17:04             ` Jonathan Morton
2015-07-31 20:23               ` Michael Richardson
2015-07-31 20:45                 ` Jonathan Morton
2015-08-03 15:44               ` dpreed
2015-08-03 16:14                 ` David Lang
2015-08-03 23:37                   ` dpreed
2015-08-03 23:52                     ` Jonathan Morton
2015-08-04  0:13                     ` David Lang
2015-08-04 16:55                       ` dpreed
2015-08-07  8:28             ` Mikael Abrahamsson
2015-08-07 13:22               ` Rich Brown
2015-08-07 13:28                 ` Jonathan Morton
2015-08-07 17:35                   ` Rich Brown
2015-08-08 14:25                     ` Simon Barber
2015-08-07 20:03                   ` David Lang
2015-08-07 21:46                     ` dpreed
2015-08-07 22:31                       ` David Lang
2015-08-08 20:46                         ` dpreed
2015-08-08 23:23                           ` David Lang
2015-08-09 19:31                             ` Jonathan Morton
2015-08-09 21:50                               ` David Lang
2015-08-10  5:39                                 ` Mikael Abrahamsson
2015-08-13 21:48                               ` David Lang
2015-08-13 22:14                                 ` Jonathan Morton
2015-08-13 22:25                                   ` David Lang
2015-08-13 22:30                                     ` Jonathan Morton
2015-08-09 22:09                           ` David Lang
2015-08-10 13:48                         ` Simon Barber

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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=A1CDC33B-5ABA-49D0-906B-13026C6395C1@gmx.de \
    --to=moeller0@gmx.de \
    --cc=alan.christopher.jenkins@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@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