From: Aaron Wood <woody77@gmail.com>
To: "Dave Täht" <dave@taht.net>
Cc: make-wifi-fast@lists.bufferbloat.net,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [Cerowrt-devel] very good book on 802.11ac stuff
Date: Tue, 9 Feb 2016 06:17:57 +0800 [thread overview]
Message-ID: <CALQXh-Pd8vDFcs__g5NyVDzOkE4oCitkX5_X60sk5mR8zVfYfA@mail.gmail.com> (raw)
In-Reply-To: <56B8F445.3070400@taht.net>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
I've often wanted the same thing: What's the time-length of given packets
(using various transmission rates), and the inter-packet delays, etc. What
_is_ 100% channel utilization, in terms of packets per second of a given
size/rate?
From a pcap file full of radio-tap-level packets, can the channel usage be
computed? (none of the tools I looked at a few years ago could give me a
channel usage indication from an analysis of actual packets (with rates and
timestamps)).
-Aaron
On Tue, Feb 9, 2016 at 4:02 AM, Dave Täht <dave@taht.net> wrote:
> Much more readable than the spec!
>
> http://chimera.labs.oreilly.com/books/1234000001739/ch03.html
>
> I still keep hoping for a comprehensive list (or a tool) for timings for
> every possible operation across all the 802.11 standards. Trying to
> figure out how long things take "on the wire" makes my brain spin.
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 1705 bytes --]
next prev parent reply other threads:[~2016-02-08 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 20:02 [Make-wifi-fast] " Dave Täht
2016-02-08 22:17 ` Aaron Wood [this message]
2016-03-12 19:20 ` [Make-wifi-fast] [Cerowrt-devel] Will full-duplex be possible on 802.11 wired air? Erkki Lintunen
2016-03-12 19:35 ` 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-Pd8vDFcs__g5NyVDzOkE4oCitkX5_X60sk5mR8zVfYfA@mail.gmail.com \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave@taht.net \
--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