From: Stephen Hemminger <stephen@networkplumber.org>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] gaming latencies
Date: Thu, 16 Dec 2021 08:39:43 -0800 [thread overview]
Message-ID: <20211216083943.60cd0331@hermes.local> (raw)
In-Reply-To: <CAA93jw62FzW0WEWQ+U3F3rkqmLE1s1E0yg=-G6KuRgDdb3xcdg@mail.gmail.com>
Apparently audiophiles are willing to spend extra money on a switch
with better power supply and carbon frame to reduce noise in digital signals.
https://www.tomshardware.com/news/ethernet-switch-for-audiophiles
prev parent reply other threads:[~2021-12-16 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 16:06 Dave Taht
2021-12-16 16:39 ` Stephen Hemminger [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=20211216083943.60cd0331@hermes.local \
--to=stephen@networkplumber.org \
--cc=bloat@lists.bufferbloat.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