General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Hans-Kristian Bakke <hkbakke@gmail.com>
To: Neal Cardwell <ncardwell@google.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Initial tests with BBR in kernel 4.9
Date: Wed, 25 Jan 2017 23:12:20 +0100	[thread overview]
Message-ID: <CAD_cGvH18Ckmzjwd_P9nsrzToTL478wXr8c-W_M-ix=pYA+uqg@mail.gmail.com> (raw)
In-Reply-To: <CADVnQykaHGTsERquHhEGptqTbCvyWcw0jFezE6eVr8KyaSmypA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 846 bytes --]

Thank you for you comments. It makes sense to me now!
I am not a member of that mailing list so feel free to repost or quote my
experiences if you feel it's relevant. I will keep it in mind for the
future though.

On 25 January 2017 at 23:02, Neal Cardwell <ncardwell@google.com> wrote:

> On Wed, Jan 25, 2017 at 5:01 PM, Neal Cardwell <ncardwell@google.com>
> wrote:
>
>> On Wed, Jan 25, 2017 at 3:54 PM, Hans-Kristian Bakke <hkbakke@gmail.com>
>> wrote:
>>
>>> Hi
>>>
>>> Kernel 4.9 finally landed in Debian testing so I could finally test BBR
>>> in a real life environment that I have struggled with getting any kind of
>>> performance out of.
>>>
>>
> BTW, these kinds of posts are ideal for the bbr-dev list, if you have any
> future test reports or discussion items:
>
>   https://groups.google.com/d/forum/bbr-dev
>
> Thanks,
> neal
>
>

[-- Attachment #2: Type: text/html, Size: 2268 bytes --]

  reply	other threads:[~2017-01-25 22:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 20:54 Hans-Kristian Bakke
2017-01-25 21:00 ` Jonathan Morton
     [not found]   ` <CAD_cGvHKw6upOCzDbHLZMSYdyuBHGyo4baaPqM7r=VvMzRFVtg@mail.gmail.com>
2017-01-25 21:09     ` [Bloat] Fwd: " Hans-Kristian Bakke
     [not found]     ` <908CA0EF-3D84-4EB4-ABD8-3042668E842E@gmail.com>
2017-01-25 21:13       ` [Bloat] " Hans-Kristian Bakke
2017-01-25 21:17         ` Jonathan Morton
2017-01-25 21:20           ` Hans-Kristian Bakke
2017-01-25 21:26             ` Jonathan Morton
2017-01-25 21:29               ` Hans-Kristian Bakke
2017-01-25 21:31                 ` Hans-Kristian Bakke
2017-01-25 21:42                   ` Jonathan Morton
2017-01-25 21:48                   ` Eric Dumazet
2017-01-25 22:03                     ` Hans-Kristian Bakke
2017-01-25 21:03 ` Hans-Kristian Bakke
2017-01-25 22:01 ` Neal Cardwell
2017-01-25 22:02   ` Neal Cardwell
2017-01-25 22:12     ` Hans-Kristian Bakke [this message]
2017-01-25 22:06   ` Steinar H. Gunderson
2017-01-25 22:12     ` Eric Dumazet
2017-01-25 22:23       ` Steinar H. Gunderson
2017-01-25 22:27         ` Eric Dumazet
2017-01-25 22:38   ` Hans-Kristian Bakke
2017-01-25 22:48     ` Neal Cardwell
2017-01-25 23:04       ` Hans-Kristian Bakke
2017-01-25 23:31         ` Hans-Kristian Bakke
2017-01-25 23:33         ` Eric Dumazet
2017-01-25 23:41           ` Hans-Kristian Bakke
2017-01-25 23:46             ` Eric Dumazet
2017-01-25 23:47           ` Hans-Kristian Bakke
2017-01-25 23:53             ` Eric Dumazet
2017-01-25 23:56               ` Hans-Kristian Bakke
2017-01-26  0:10                 ` Eric Dumazet

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='CAD_cGvH18Ckmzjwd_P9nsrzToTL478wXr8c-W_M-ix=pYA+uqg@mail.gmail.com' \
    --to=hkbakke@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=ncardwell@google.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