From: Aaron Wood <woody77@gmail.com>
To: erik.taraldsen@telenor.com
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
brouer@redhat.com, lumuscar@cisco.com, priyarjha@google.com,
marek@cloudflare.com, bloat <bloat@lists.bufferbloat.net>,
colrack@gmail.com
Subject: Re: [Bloat] BBR implementations, knobs to turn?
Date: Mon, 30 Nov 2020 09:18:21 -0800 [thread overview]
Message-ID: <CALQXh-PUDSoHyqPud5aNStm1ov47Uqg5EijwTpQh+nikM_UhRQ@mail.gmail.com> (raw)
In-Reply-To: <1606136220411.40216@telenor.com>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
>
> The CPE side has met willingness to investigate these issues from early
> on, but it seems that buffer handling is much harder on CPE chipsets
> than on base station chipsets. In particular on 5G. We have had some
> very good results on 4G, but they do not translate to 5G.
>
My own experience with various CPE work (working with ODMs to get hardware
built) is that those building CPE are stuck with what the silicon vendors
will support, much like where we currently are with home routers. The AP
firmware and drivers have bloated buffers and there's very little that can
be done to change that.
The large OEMs (the very large, well-known, retail brands) have the volume
to put pressure on the silicon vendors to fix this. But there's not much
incentive for a silicon vendor to address this issue for a smaller customer.
[-- Attachment #2: Type: text/html, Size: 1130 bytes --]
next prev parent reply other threads:[~2020-11-30 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 15:25 erik.taraldsen
2020-11-16 21:14 ` Neal Cardwell
2020-11-17 10:05 ` erik.taraldsen
2020-11-17 15:07 ` Jesper Dangaard Brouer
2020-11-19 7:57 ` erik.taraldsen
2020-11-19 13:32 ` Luca Muscariello
2020-11-19 14:35 ` erik.taraldsen
2020-11-20 11:10 ` Jesper Dangaard Brouer
2020-11-20 12:42 ` Toke Høiland-Jørgensen
2020-11-23 12:57 ` erik.taraldsen
2020-11-30 17:18 ` Aaron Wood [this message]
2020-11-20 23:34 ` Neal Cardwell
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=CALQXh-PUDSoHyqPud5aNStm1ov47Uqg5EijwTpQh+nikM_UhRQ@mail.gmail.com \
--to=woody77@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=brouer@redhat.com \
--cc=colrack@gmail.com \
--cc=erik.taraldsen@telenor.com \
--cc=lumuscar@cisco.com \
--cc=marek@cloudflare.com \
--cc=priyarjha@google.com \
--cc=toke@toke.dk \
/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