From: Jonathan Morton <chromatix99@gmail.com>
To: Azin Neishaboori <azin.neishaboori@gmail.com>
Cc: bloat-devel@lists.bufferbloat.net
Subject: Re: monitoring queue length
Date: Sat, 1 Dec 2018 09:47:15 +0200 [thread overview]
Message-ID: <7ACB9F40-A42B-4807-85EF-10500F11E437@gmail.com> (raw)
In-Reply-To: <CADXq5+8Av3L6ABV1nscV-Zth3A0MekHnoMPp9xT0+EK13JHpOg@mail.gmail.com>
> On 1 Dec, 2018, at 9:37 am, Azin Neishaboori <azin.neishaboori@gmail.com> wrote:
>
> So based on the dumbbell topology you described, I should see queue buildup at the egress cellular interface of the router, right?
Yes - but the actual cellular interface is on the far side of a translation device, and so its queue is hidden from Linux. That's unfortunately true of *every* 3G or LTE interface I've yet seen. Older devices have a virtual serial PPP interface to the translator, newer ones pretend to be Ethernet devices on the near side of the translator - in both cases with much more bandwidth than the cellular interface itself.
This is actually quite a serious problem for people trying to improve the quality of cellular Internet connections. All of the low-level stuff that would be useful to experiment with is deliberately and thoroughly hidden.
If you put in an artificial bottleneck of 10Mbps on the outgoing interface, you should be able to develop a queue there. You can use HTB or HFSC, with the qdisc of your choice as a child on which the actual queuing occurs.
A better way to measure the impact of queuing in the raw device is to observe the increase of latency when the link is loaded versus when it is idle. I recommend using the Flent tool for that.
- Jonathan Morton
next prev parent reply other threads:[~2018-12-01 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 22:05 Azin Neishaboori
2018-12-01 3:13 ` Jonathan Morton
2018-12-01 7:37 ` Azin Neishaboori
2018-12-01 7:47 ` Jonathan Morton [this message]
2018-12-01 8:04 ` Azin Neishaboori
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=7ACB9F40-A42B-4807-85EF-10500F11E437@gmail.com \
--to=chromatix99@gmail.com \
--cc=azin.neishaboori@gmail.com \
--cc=bloat-devel@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