From: "Jonas Mårtensson" <martensson.jonas@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] 22 seconds til bloat on gfiber?
Date: Mon, 24 Oct 2016 18:57:37 +0200 [thread overview]
Message-ID: <CAM9iV=+9p_gyoTi-HqVD6pGpJ7aQx6gorzxEyDXV=DQmFmsdVg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1610230747060.12036@uplift.swm.pp.se>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
On Sun, Oct 23, 2016 at 7:50 AM, Mikael Abrahamsson <swmike@swm.pp.se>
wrote:
> On Sat, 22 Oct 2016, Dave Taht wrote:
>
> http://www.dslreports.com/speedtest/5408767
>>
>
> What's the setup here? Someone has told me that Google Fiber is PON? So
> there is an ONT at the customer prem which takes fiber and hands off some
> kind of 1GBASE-T? What more?
>
> Just trying to figure out what device has ~13-15 megabyte buffer so it can
> induce 1200ms buffer lag at 1 gigabit/s.
Of course I don't know the setup in this particular case but from what I've
heard, gfiber is mostly GPON with 1:16 splits. They have used different ONT
versions but the "current" generation seems to be a custom ONT from an ODM:
https://support.google.com/fiber/answer/6035992?hl=en&ref_topic=2667450
https://wikidevi.com/wiki/Google_Fiber_Jack_v2_(GFLT110)
Also, this may be interesting:
https://gfiber-review.googlesource.com/#/c/1232/
[-- Attachment #2: Type: text/html, Size: 1861 bytes --]
next prev parent reply other threads:[~2016-10-24 16:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 21:56 Dave Taht
2016-10-22 23:52 ` Jonathan Morton
2016-10-23 1:33 ` jb
2016-10-23 1:45 ` Dave Taht
2016-10-23 1:47 ` Dave Taht
2016-10-23 2:27 ` jb
[not found] ` <CAJq5cE3DsV9v6ATVeq+vF_kVFjKy+8Qjwe-P01ZZbyKZB9HC6w@mail.gmail.com>
2016-10-23 8:29 ` Jonathan Morton
2016-10-23 9:23 ` jb
2016-10-23 16:14 ` Klatsky, Carl
2016-10-24 0:46 ` jb
2016-10-24 13:13 ` Klatsky, Carl
2016-10-24 16:11 ` Noah Causin
2016-10-24 20:27 ` Klatsky, Carl
2016-10-23 2:30 ` Benjamin Cronce
2016-10-25 7:10 ` Jonas Mårtensson
2016-10-23 5:50 ` Mikael Abrahamsson
2016-10-24 16:57 ` Jonas Mårtensson [this message]
2016-10-24 22:10 ` Benjamin Cronce
2016-10-25 0:09 ` jb
2016-10-25 12:01 ` Benjamin Cronce
2016-10-25 13:11 ` Klatsky, Carl
2016-10-25 21:20 ` jb
2016-10-26 0:02 ` Klatsky, Carl
2016-10-25 15:59 ` Jan Ceuleers
2016-10-26 1:05 ` Benjamin Cronce
2016-10-26 14:49 ` Jan Ceuleers
2016-10-26 15:36 ` Mikael Abrahamsson
2016-10-27 14:32 ` Jonas Mårtensson
2016-10-27 16:56 ` Dave Taht
2016-10-27 17:56 ` [Bloat] Sidebar on s-curves David Collier-Brown
2016-10-27 19:30 ` [Bloat] 22 seconds til bloat on gfiber? David Lang
2016-10-27 19:41 ` Dave Taht
2016-10-27 19:48 ` Aaron Wood
2016-10-28 15:51 ` Jan Ceuleers
2016-10-28 15:55 ` Klatsky, Carl
2016-10-27 19:45 ` Aaron Wood
2016-10-27 20:17 ` Mikael Abrahamsson
2016-12-07 5:40 ` Jonathan Morton
2016-12-07 7:05 ` Mikael Abrahamsson
[not found] <mailman.313.1477591111.3555.bloat@lists.bufferbloat.net>
2016-10-27 19:27 ` Jonathan Foulkes
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='CAM9iV=+9p_gyoTi-HqVD6pGpJ7aQx6gorzxEyDXV=DQmFmsdVg@mail.gmail.com' \
--to=martensson.jonas@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=swmike@swm.pp.se \
/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