General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Kathleen Nichols <nichols@pollere.com>
To: Eric Dumazet <eric.dumazet@gmail.com>, Jim Gettys <jg@freedesktop.org>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] passive network delay monitoring utility
Date: Fri, 26 May 2017 10:31:14 -0700	[thread overview]
Message-ID: <4583ea17-8e19-310e-078c-8519b04df146@pollere.com> (raw)
In-Reply-To: <1495569054.6465.77.camel@edumazet-glaptop3.roam.corp.google.com>


Eric,

You are the king of Making The Right Thing Happen.

	Kathie

On 5/23/17 12:50 PM, Eric Dumazet wrote:
> I had the honor to attend Kathleen presentation at Google ;)
> 
> I then worked on making sure TCP TS TSval  would use 1ms units,
> regardless of CONFIG_HZ option in the kernel, since apparently some
> distros/devices use HZ=250 or even HZ=100
> 
> This should be in linux-4.13 when released.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=9a568de4818dea9a05af141046bd3e589245ab83
> 
> Cover letter for the patch series :
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=e26925ec03b31f5ae4c1fc544515486229334ef9
> 
> 
> On Tue, 2017-05-23 at 15:22 -0400, Jim Gettys wrote:
>> Those of you who have not looked at pping should do so.
>>
>>
>> See: http://pollere.net/pping.html for a description, and look at the
>> slides linked to on that page.
>>
>>
>> In particular, it would be sweet to run this on a home router, as you
>> can monitor latency simultaneously in either direction.  Then we can
>> point a finger properly at the ISP or at the WiFi in the home network
>> (encouraging either/both to get fixed).
>>
>>
>> Anyone interested in undertaking such a project with me, please drop
>> me a note.
>>
>>
>> The only downside is that pping is a C++ app, which makes it big for a
>> home router, so it can't be used on old small home routers due to
>> footprint issues; but many current home routers would have space for
>> it.
>>
>>
>>                                                  - Jim
>>
>>
>>
>>
>>
>>
>>
>> On Sun, Apr 30, 2017 at 8:41 PM, Kathleen Nichols
>> <nichols@pollere.com> wrote:
>>         
>>         Hi,
>>         I've just made one of the tools I use to measure network delay
>>         available with a GPLv2 license. Perhaps it will be of
>>         intererst.
>>         
>>         https://github.com/pollere/pping
>>         
>>                 Kathie
>>         _______________________________________________
>>         Bloat mailing list
>>         Bloat@lists.bufferbloat.net
>>         https://lists.bufferbloat.net/listinfo/bloat
>>
>>
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
> 
> 


  reply	other threads:[~2017-05-26 17:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01  0:41 Kathleen Nichols
2017-05-23 19:22 ` Jim Gettys
2017-05-23 19:50   ` Eric Dumazet
2017-05-26 17:31     ` Kathleen Nichols [this message]
2017-05-26 18:41   ` Kathleen Nichols

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=4583ea17-8e19-310e-078c-8519b04df146@pollere.com \
    --to=nichols@pollere.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=eric.dumazet@gmail.com \
    --cc=jg@freedesktop.org \
    /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