From: Loganaden Velvindron <loganaden@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] 3g/4g with fq_codel & mobility
Date: Tue, 22 Nov 2016 22:34:27 +0400 [thread overview]
Message-ID: <CAOp4FwRUWqBWNXbm_6SXFsz3bqUxusrz+-zBGWuHzpHe5pPiRQ@mail.gmail.com> (raw)
In-Reply-To: <97DE7A30-F225-4B9C-B84B-DD3C38F35A69@gmail.com>
On Mon, Nov 21, 2016 at 3:27 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 21 Nov, 2016, at 13:16, Loganaden Velvindron <loganaden@gmail.com> wrote:
>>
>> I have one of those gl.inet 6416a board. It runs fq_codel on the
>> USB-3g dongle modem interface, and it runs very well at rest.
>>
>> I put it inside a car, and while driving, I notice some induced latency:
>>
>> https://www.dslreports.com/speedtest/6354936
>>
>> Can someone who has some understanding of 3g/4g internals shed some
>> light ? Could the 3g/4g modem be buffering due to varying strength of
>> the signal or due to handover in base station ?
>
> Usually such dongles don’t give direct access to the 3G modem interface. Instead they provide an Ethernet or PPP interface, and do a conversion internally. Ethernet emulation is more common of late, possibly due to the rise of 4G.
>
> Running fq_codel on such a device without a shaper relies on the buffers in *both* the dongle itself and the driver for the emulated Ethernet device having appropriately sized buffers in aggregate. This is virtually never the case. And that’s just for the upload direction.
>
> In the download direction you are relying on buffers in the provider’s network and the cell tower. Fq_codel on your own hardware has no effect here.
>
I think that reducing the buffer size with NCM might be a good start,
particularly with 4G. THere is a lot of work to be done on the
USB-ethernet stack.
prev parent reply other threads:[~2016-11-22 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 11:16 Loganaden Velvindron
2016-11-21 11:27 ` Jonathan Morton
2016-11-22 18:34 ` Loganaden Velvindron [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=CAOp4FwRUWqBWNXbm_6SXFsz3bqUxusrz+-zBGWuHzpHe5pPiRQ@mail.gmail.com \
--to=loganaden@gmail.com \
--cc=chromatix99@gmail.com \
--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