General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: toke@toke.dk
Cc: "Stephen Hemminger" <stephen@networkplumber.org>,
	"Toke Høiland-Jørgensen via Bloat" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Comparing bufferbloat tests (was: We built a new bufferbloat test and keen for feedback)
Date: Fri, 6 Nov 2020 18:05:46 +0100	[thread overview]
Message-ID: <trinity-53a022bc-5d4b-4233-b49c-b5f2b6ff9198-1604682346801@3c-app-gmx-bs15> (raw)
In-Reply-To: <87k0uyfojb.fsf@toke.dk>

Hi Toke,

> Gesendet: Freitag, 06. November 2020 um 17:17 Uhr
> Von: "Toke Høiland-Jørgensen via Bloat" <bloat@lists.bufferbloat.net>
> An: "Stephen Hemminger" <stephen@networkplumber.org>, "Toke Høiland-Jørgensen via Bloat" <bloat@lists.bufferbloat.net>
> Betreff: Re: [Bloat] Comparing bufferbloat tests (was: We built a new bufferbloat test and keen for feedback)
>
> Stephen Hemminger <stephen@networkplumber.org> writes:
> 
> > PS: Why to US providers have such asymmetric bandwidth? Getting something symmetric
> > requires going to a $$$ business rate.
> 
> For Cable, the DOCSIS standard is asymmetric by design, but not *that*
> asymmetric. 

       Unfortunately is is that bad: DOCSIS 3.0 Downstream 108 MHz to 1002 MHz Upstream 30 MHz to 85 MHz, so (1002-108)/(85-30) 16:1, but not all cable co, have matching upstream filters for 85MHz. Then again, the two ACK per two full segment rule puts a lower end in, with what an ISP can get away, if the customer is expected to at least see the downstream rate in speedtests, I can never remember whether that is essentially 20:1 or 40:1, but since then GRO?GSO and friends, as well as ACK filtering has reduced the ACK traffic somewhat...


> I *think* the rest is because providers have to assign
> channels independently for upstream and downstream, and if they just
> assign them all to downstream they can advertise a bigger number...

       They wished, once they deploy upstream amplifiers these have a fixed frequency split and need to be replaced if the spilt is changed, that gets expensive quickly... or so I have heard.

Best Regards
        Sebastian

> 
> -Toke
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

  reply	other threads:[~2020-11-06 17:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 21:30 [Bloat] We built a new bufferbloat test and keen for feedback Sam Westwood
2020-11-04 23:43 ` Michael Richardson
2020-11-04 23:54 ` Toke Høiland-Jørgensen
2020-11-05  1:52   ` Y
2020-11-05  0:23 ` Dave Collier-Brown
2020-11-05 11:48   ` Toke Høiland-Jørgensen
2020-11-05 13:24     ` [Bloat] Comparing bufferbloat tests (was: We built a new bufferbloat test and keen for feedback) Dave Collier-Brown
2020-11-05 14:24       ` Toke Høiland-Jørgensen
2020-11-05 16:06         ` Arshan Khanifar
2020-11-05 17:25           ` Toke Høiland-Jørgensen
2020-11-06 16:03             ` Stephen Hemminger
2020-11-06 16:17               ` Toke Høiland-Jørgensen
2020-11-06 17:05                 ` Sebastian Moeller [this message]
2020-11-08 22:07             ` Arshan Khanifar
2020-11-14  3:37               ` Dave Taht
2020-11-14 23:14                 ` Michael Richardson
2020-11-05  8:21 ` [Bloat] We built a new bufferbloat test and keen for feedback Sebastian Moeller
2020-11-05 21:30 ` Sam

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=trinity-53a022bc-5d4b-4233-b49c-b5f2b6ff9198-1604682346801@3c-app-gmx-bs15 \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=stephen@networkplumber.org \
    --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