From: Jonathan Morton <chromatix99@gmail.com>
To: Jaap Buurman <jaapbuurman@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Major Bufferbloat
Date: Mon, 27 Mar 2017 14:45:53 +0300 [thread overview]
Message-ID: <4FD02E40-E6F4-4D3D-A12A-EA73080256A5@gmail.com> (raw)
In-Reply-To: <CAN-r--mhqXzC0KsS5mA74G7wPTA6q-_cSTBv3zGq9TbaU0GaHw@mail.gmail.com>
> On 27 Mar, 2017, at 14:41, Jaap Buurman <jaapbuurman@gmail.com> wrote:
>
> a high number of concurrent data streams from my wireless-n client to my router
In that case, the bufferbloat is probably in your client, rather than in the router. Details of that device may aid diagnosis.
- Jonathan Morton
next prev parent reply other threads:[~2017-03-27 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 11:41 Jaap Buurman
2017-03-27 11:45 ` Jonathan Morton [this message]
2017-03-27 11:46 ` Toke Høiland-Jørgensen
2017-03-27 11:56 ` Jaap Buurman
2017-03-27 12:21 ` Jonathan Morton
2017-03-27 13:41 ` Jaap Buurman
2017-03-27 14:25 ` marty
2017-03-27 14:54 ` marty
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FD02E40-E6F4-4D3D-A12A-EA73080256A5@gmail.com \
--to=chromatix99@gmail.com \
--cc=jaapbuurman@gmail.com \
--cc=make-wifi-fast@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