From: Stephen Hemminger <stephen@networkplumber.org>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] [Bloat] QCut - "Understanding on-device bufferbloat for cellular upload", Guo et al
Date: Tue, 15 Nov 2016 10:36:05 -0800 [thread overview]
Message-ID: <20161115103605.02904558@samsung9> (raw)
In-Reply-To: <156EE814-3742-4F23-99AC-7905077B1803@gmail.com>
On Tue, 15 Nov 2016 12:00:29 -0500
Rich Brown <richb.hanover@gmail.com> wrote:
> Google Alerts sent a link to this paper: "Understanding on-device bufferbloat for cellular upload" available at: http://dl.acm.org/citation.cfm?id=2987490 (ACM Paywall...)
>
> In my two-minute skim of the paper, I see they describe how latency gets bad on cellular devices (no kidding) and then propose QCut, a queue inserted between the qdisc and the hardware. They say:
>
> ---
> ... QCut operates in the kernel space and takes as input only information of buffer occupancy and transmission statistics, which is exposed by most cellular radio firmware from Qualcomm and likely other vendors.
>
> Since directly limiting the firmware buffer occupancy is difficult, QCut controls the firmware queuing delay indirectly in the kernel by controlling how fast packets from Qdisc flow into the firmware buffer. QCUT estimates the radio firmware buffer occupancy and queuing delay to decide the transmission of packets to the firmware dynamically...
> ---
>
> Their analysis and charts show that QCut helps a lot.
>
> I found it interesting that they make measurements with both weak and strong signal strength, to indicate the hits that are caused by differing signal strength.
>
> Enjoy!
>
> Rich
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
Reinvention of BQL?
prev parent reply other threads:[~2016-11-15 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 17:00 [Make-wifi-fast] " Rich Brown
2016-11-15 18:36 ` Stephen Hemminger [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/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=20161115103605.02904558@samsung9 \
--to=stephen@networkplumber.org \
--cc=bloat@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=richb.hanover@gmail.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