From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] gaming routers...
Date: Wed, 4 Jan 2017 13:45:55 -0800 [thread overview]
Message-ID: <CALQXh-Mtn8nKHHBGYsGpmaRzhv59N0cPTcASvVOMpSSDfX=Png@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5WLumCx1QBAgD785KDtu5PNOBi+UaXtnDE-3JtSn8bBw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
"but it has revealed that the WRT32X is designed to automatically detect
computers using the Killer-line of network adapters
<http://www.killernetworking.com/>, indicating it's probably a
gaming-focused PC from a company like Alienware, MSI, or Razer that
requires priority access to the home's internet. It does the same thing for
an Xbox as well, if console gaming is more your thing."
Or it's looking at the mac ids of the devices, and queuing them separately,
with higher priority, but throttled to a percentage of overall bandwidth.
Much like the Cisco recommendations for voip traffic using EF.
-Aaron
On Wed, Jan 4, 2017 at 1:37 PM, Dave Taht <dave.taht@gmail.com> wrote:
> My guess is, of course, that this is some snoopy set of optimizations,
> but who knows,
> perhaps they were paying attention to fq_codel...
>
> http://www.kotaku.com.au/2017/01/linksyss-new-router-puts-
> video-games-first/
>
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 2723 bytes --]
next prev parent reply other threads:[~2017-01-04 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 21:37 Dave Taht
2017-01-04 21:45 ` Aaron Wood [this message]
2017-01-04 21:57 ` Jonathan Morton
2017-01-05 0:49 ` Aaron Wood
2017-01-05 11:04 ` Toke Høiland-Jørgensen
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='CALQXh-Mtn8nKHHBGYsGpmaRzhv59N0cPTcASvVOMpSSDfX=Png@mail.gmail.com' \
--to=woody77@gmail.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