From: Jonathan Morton <chromatix99@gmail.com>
To: d@taht.net (Dave Täht)
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Bufferbloat and Internet gaming
Date: Sat, 12 Mar 2011 23:28:23 +0200 [thread overview]
Message-ID: <AF0F263A-EBB0-4829-8EE8-9D2EFF979954@gmail.com> (raw)
In-Reply-To: <8762rol4a8.fsf_-_@cruithne.co.teklibre.org>
On 12 Mar, 2011, at 5:58 pm, Dave Täht wrote:
>> John Carmack
I wonder if anyone here has any experience with the "KillerNIC" that I saw being reviewed a year or two ago? Looking at the Bigfoot website, it seems they have at least half a clue but might not understand all of the underlying causes.
http://www.bigfootnetworks.com/technology#gane
It's not clear whether it does any management of TCP traffic, besides locally prioritising it behind UDP.
- Jonathan
prev parent reply other threads:[~2011-03-12 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87sjv1bj50.fsf@cruithne.co.teklibre.org>
[not found] ` <ACE3C2B383A165488DDCB320EC6A3A6842D1EE67@Exchange.eden.idsoftware.com>
2011-03-12 15:58 ` Dave Täht
2011-03-12 21:28 ` Jonathan Morton [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=AF0F263A-EBB0-4829-8EE8-9D2EFF979954@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=d@taht.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