From: Aaron Wood <woody77@gmail.com>
To: David Lang <david@lang.hm>
Cc: Michal Kazior <michal.kazior@tieto.com>,
make-wifi-fast@lists.bufferbloat.net,
"codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] [Make-wifi-fast] [RFC/RFT] mac80211: implement fq_codel for software queuing
Date: Tue, 22 Mar 2016 03:14:03 -0000 [thread overview]
Message-ID: <CALQXh-N+Y_r-YeU8_L6w2=dSb5wK4JR6a90Nu_UhdAmJK2gUDg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1603211827190.26766@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
On Mon, Mar 21, 2016 at 6:29 PM, David Lang <david@lang.hm> wrote:
> On Mon, 29 Feb 2016, Michal Kazior wrote:
>
> Our intent is to continue to improve the flent test suite to be able
>>> to generate repeatable tests, track relevant wifi behaviors and pull
>>> relevant data back, graphed over time (of test) and time (over test
>>> runs). A problem with udp flood tests is that tcp traffic is always
>>> bidirectional (data vs acks), so a naive thought would be, that yes,
>>> you should get half the bandwidth you get with a udp flood test.
>>>
>>
>> I don't see why you'd be doomed to get only half the bandwidth because
>> of that? Sure, Wi-Fi is half-duplex but transmit time for ACKs is a
>> lot smaller than transmit time for the data.
>>
>
> The difference is actually far less than you think. Each transmission has
> a fixed-length header and quiet times that were designed in the days of
> 802.11b (1-11Mb) and if you are transmitting a wide 802.11ac signal at a
> couple hundred Mb, you can find that the time taken to transmit even full
> packets is a surprisingly small percentage of the total transmit time.
>
> David Lang
A 2-dimensional display of data sent vs. time might be useful, for a couple
packets, to help explain this (although it may need to be at log-scale).
X-axis is time, Y is bandwidth being sent.
-Aaron
[-- Attachment #2: Type: text/html, Size: 2016 bytes --]
prev parent reply other threads:[~2016-03-22 3:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1456492163-11437-1-git-send-email-michal.kazior@tieto.com>
2016-02-26 14:32 ` [Codel] Fwd: " Dave Taht
2016-02-26 19:27 ` [Codel] " Michal Kazior
2016-02-26 22:20 ` Dave Taht
2016-02-29 12:35 ` Michal Kazior
2016-03-22 1:29 ` [Codel] [Make-wifi-fast] " David Lang
2016-03-22 3:14 ` Aaron Wood [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/codel.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-N+Y_r-YeU8_L6w2=dSb5wK4JR6a90Nu_UhdAmJK2gUDg@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=michal.kazior@tieto.com \
/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