From: "David P. Reed" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] 10gige and 2.5gige
Date: Thu, 16 Dec 2021 13:16:55 -0500 (EST) [thread overview]
Message-ID: <1639678615.275317887@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw6i0G_QyBbmC_0U-UUc4y3kZnb_vdvGpo1WE6m9pfDDWQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2172 bytes --]
Yes, it's very cheap and getting cheaper.
Since its price fell to the point I thought was cheap, my home has a 10 GigE fiber backbone, 2 switches in my main centers of computers, lots of 10 GigE NICs in servers, and even dual 10 GigE adapters in a Thunderbolt 3 external adapter for my primary desktop, which is a Skull Canyon NUC.
I strongly recommend people use fiber and sfp+ DAC cabling because twisted pair, while cheaper, actually is problematic at speeds above 1 Gig - mostly due to power and heat.
BTW, it's worth pointing out that USB 3.1 can handle 10 Gb/sec, too, and USB-C connectors and cables can carry Thunderbolt at higher rates. Those adapters are REALLY CHEAP. There's nothing inherently different about the electronics, if anything, USB 3.1 is more complicate logic than the ethernet MAC.
So the reason 10 GigE is still far more expensive than USB 3.1 is mainly market volume - if 10 GigE were a consumer product, not a datacenter product, you'd think it would already be as cheap as USB 3.1 in computers and switches.
Since DOCSIS can support up to 5 Gb/s, I think, when will Internet Access Providers start offering "Cable Modems" that support customers who want more than "a full Gig"? Given all the current DOCSIS 3 CMTS's etc. out there, it's just a configuration change.
So when will consumer "routers" support 5 Gig, 10 Gig?
On Thursday, December 16, 2021 11:20am, "Dave Taht" <dave.taht@gmail.com> said:
> has really got cheap.
>
> https://www.tomshardware.com/news/innodisk-m2-2280-10gbe-adapter
>
> On the other hand users are reporting issues with actually using
> 2.5ghz cable with this router in particular, halving the achieved rate
> by negotiating 2.5gbit vs negotiating 1gbit.
>
> https://forum.mikrotik.com/viewtopic.php?t=179145#p897836
>
>
> --
> I tried to build a better future, a few times:
> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 4014 bytes --]
next prev parent reply other threads:[~2021-12-16 18:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 16:20 Dave Taht
2021-12-16 18:16 ` David P. Reed [this message]
2021-12-16 19:31 ` Joel Wirāmu Pauling
2021-12-16 21:29 ` David P. Reed
2021-12-16 21:43 ` David Lang
2021-12-16 21:57 ` Joel Wirāmu Pauling
2021-12-17 8:18 ` Sebastian Moeller
2021-12-17 8:36 ` Joel Wirāmu Pauling
2021-12-17 8:39 ` Joel Wirāmu Pauling
2021-12-17 9:26 ` Sebastian Moeller
2021-12-17 11:33 ` Toke Høiland-Jørgensen
2021-12-17 8:57 ` Sebastian Moeller
2021-12-19 18:07 ` David P. Reed
2021-12-23 1:17 ` Aaron Wood
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1639678615.275317887@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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