From: Ben Greear <greearb@candelatech.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: bloat-devel@lists.bufferbloat.net, johannes@sipsolutions.net,
linux-wireless@vger.kernel.org,
"Nathaniel J. Smith" <njs@pobox.com>
Subject: Re: [RFC] mac80211: implement eBDP algorithm to fight bufferbloat
Date: Wed, 16 Feb 2011 19:31:05 -0800 [thread overview]
Message-ID: <4D5C9679.3060700@candelatech.com> (raw)
In-Reply-To: <1297907356-3214-1-git-send-email-linville@tuxdriver.com>
On 02/16/2011 05:49 PM, John W. Linville wrote:
> This is an implementation of the eBDP algorithm as documented in
> Section IV of "Buffer Sizing for 802.11 Based Networks" by Tianji Li,
> et al.
>
> http://www.hamilton.ie/tianji_li/buffersizing.pdf
>
> This implementation timestamps an skb before handing it to the hardware
> driver, then computes the service time when the transmit status is
> reported back from the driver. An exponentially weighted moving
> average of per packet service times is used to restrict queueing
> delays in hopes of achieving a target packet transmission latency.
>
> Signed-off-by: John W. Linville<linville@tuxdriver.com>
> ---
> This is preliminary, but it seems to put some limits on latencies
> for me. I haven't even really done much testing, so YMMV...
>
> I'm sure this isn't ideal. This should be combined with the ALT
> algorithm to yield the A* algorithm. There are parameters that
> probably should be tunable (or at least better researched). This may
> not be ideal for 802.11n -- it may even be detrimental to it.
>
> Still, it is an attempt at addressing buffer bloat. Plus, it should
> pertain to all mac80211-based drivers. So, feel free to test it,
> suggest different parameters, report real numbers, post patches,
> etc... :-)
> + /* test for queue admission qualifications */
> + tserv_ns_avg = ewma_read(&sdata->tserv_ns_avg);
> + /* constants 2 msec and offset 5 should be tunable? */
> + max_enqueued = 2 * NSEC_PER_MSEC / tserv_ns_avg + 5;
> + if (atomic_read(&sdata->enqueued)> max_enqueued) {
> + /* silently drop */
> + dev_kfree_skb(skb);
> + return IEEE80211_TX_OK;
> + }
We should have some visible stat to increment when you drop on xmit,
tx-fifo error or similar?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-02-17 3:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1297619803-2832-1-git-send-email-njs@pobox.com>
2011-02-17 1:49 ` John W. Linville
2011-02-17 3:31 ` Ben Greear [this message]
2011-02-17 4:26 ` Nathaniel Smith
2011-02-17 8:31 ` Johannes Berg
2011-02-18 21:21 ` [RFC v2] " John W. Linville
2011-02-19 3:44 ` Nathaniel Smith
2011-02-21 18:47 ` John W. Linville
2011-02-21 23:26 ` Nathaniel Smith
2011-02-23 22:28 ` John W. Linville
2011-02-25 18:21 ` Nathaniel Smith
2011-02-25 18:27 ` Nathaniel Smith
2011-02-20 0:37 ` Nathaniel Smith
2011-02-20 0:51 ` Jim Gettys
2011-02-20 15:24 ` Dave Täht
2011-02-21 18:52 ` John W. Linville
2011-02-21 15:28 ` Johannes Berg
2011-02-21 16:12 ` Jim Gettys
2011-02-21 19:15 ` John W. Linville
2011-02-21 19:06 ` John W. Linville
2011-02-21 19:29 ` [RFC v2] mac80211: implement eBDP algorithm to fight bufferbloat - AQM on hosts Jim Gettys
2011-02-21 20:26 ` [RFC v2] mac80211: implement eBDP algorithm to fight bufferbloat Tianji Li
2011-02-28 13:07 ` Johannes Berg
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D5C9679.3060700@candelatech.com \
--to=greearb@candelatech.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=njs@pobox.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