From: Jim Gettys <jg@freedesktop.org>
To: Kathleen Nichols <nichols@pollere.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] lte + cable latency improvement
Date: Tue, 15 Jan 2019 10:27:15 -0500 [thread overview]
Message-ID: <CAGhGL2C1V-EGV=JSNKxOpctP91kDED3fFkyfu1w9x17Zw3qaRg@mail.gmail.com> (raw)
In-Reply-To: <8ca74fdb-0618-f04f-9ba2-801e7b235c60@pollere.net>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
On Tue, Jan 15, 2019 at 10:04 AM Kathleen Nichols <nichols@pollere.net>
wrote:
> On 1/15/19 12:02 AM, Dave Taht wrote:
> >
> https://www.cablelabs.com/enabling-the-cable-networks-for-mobile-backhaul/
> >
> >
>
> Hmm. From the linked article:
>
> > Additionally, in building the PoC, we have accumulated expertise on
> > how to perfect the BWR algorithm to optimally predict the amount of
> > data and time egressed from the LTE side. We will pass this knowledge
> > on to the LTE implementers during the specification work.
>
> So they can optimally predict the traffic they "loaded [it] up" with.
> Dave, you see why I am skeptical of fake traffic.
>
Not to mention the fact the LTE traffic is distorted badly by its own
sources of bufferbloat...
However, getting LTE implementers to understand that the problem exists in
the first place is worthwhile (so long
as they understand it can occur in either/both parts of the path...
JIm
>
> _____________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 2272 bytes --]
prev parent reply other threads:[~2019-01-15 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 8:02 Dave Taht
2019-01-15 15:04 ` Kathleen Nichols
2019-01-15 15:27 ` Jim Gettys [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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGhGL2C1V-EGV=JSNKxOpctP91kDED3fFkyfu1w9x17Zw3qaRg@mail.gmail.com' \
--to=jg@freedesktop.org \
--cc=bloat@lists.bufferbloat.net \
--cc=nichols@pollere.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