General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: jb <justin@dslr.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] bufferbloat at high edge rates
Date: Wed, 16 Nov 2016 10:16:46 +1100	[thread overview]
Message-ID: <CAH3Ss96Mbhb+1pcz4UzBEph1o+WvBbSifWFThBXLP7BHXGjqYA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5kqG2v48+6ryzzOuufJy1C=Md4ymyU_A3Crkq6O-KdnQ@mail.gmail.com>

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

Yeah sorry the forum software zipped up the attachment and thus loses the
executable permission flags. I'll attach zips to the post instead which I
think will fix that.


file *amd64

dslrcli-darwin-amd64:  Mach-O 64-bit executable x86_64

dslrcli-freebsd-amd64: ELF 64-bit LSB executable, x86-64, version 1
(FreeBSD), statically linked, not stripped

dslrcli-linux-amd64:   ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
statically linked, not stripped

dslrcli-netbsd-amd64:  ELF 64-bit LSB executable, x86-64, version 1
(NetBSD), statically linked, for NetBSD 5.99, not stripped


On Wed, Nov 16, 2016 at 3:22 AM, Dave Taht <dave.taht@gmail.com> wrote:

> On Mon, Nov 14, 2016 at 12:06 PM, Kathleen Nichols <nichols@pollere.com>
> wrote:
> >
> > My measurements are showing those kinds of delays are in the client
> > network but I don't know enough about this set up to know what's
> > going on.
> >
> > If anyone is interested, I'm talking about some recent measurements at
> > the IRTG MAPRG meeting that is Thursday morning Korea time. I'm
> > guessing there's not much interest though since I had no comments on the
> > prevn fus measurements though a fair number of people downloaded my
> > writeup.
>
> Well, getting in front of an audience always helps.
>
> Break a leg! (and please post a link to the video and slides when done!)
>
> >         Kathie
> >
> >
> > On 11/14/16 11:02 AM, Dave Taht wrote:
> >> I do keep hoping it's really the browsers misbehaving.
> >>
> >> http://www.dslreports.com/speedtest/6054627
> >>
> >>
> >
>
>
>
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

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

  reply	other threads:[~2016-11-15 23:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 19:02 Dave Taht
2016-11-14 20:06 ` Kathleen Nichols
2016-11-15 16:22   ` Dave Taht
2016-11-15 23:16     ` jb [this message]
2016-11-15  0:11 ` jb
2016-11-15  0:31   ` Dave Taht
2016-11-15  0:36     ` Jonathan Morton
2016-11-15 15:23   ` James Cloos
2016-11-15 15:43     ` Jan Ceuleers
2016-11-16  0:34   ` David Lang
2016-11-16  4:09     ` jb
2016-11-16  6:00       ` Stefan Alfredsson
2016-11-16 11:26         ` Stefan Alfredsson
2016-11-16 20:27         ` jb
2016-11-16  6:02       ` David Lang
     [not found]       ` <CY4PR04MB05665A2EFEB8CE55866C839A95BE0@CY4PR04MB0566.namprd04.prod.outlook.com>
2016-11-17  0:16         ` jb
2016-11-17  7:50           ` David Lang

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=CAH3Ss96Mbhb+1pcz4UzBEph1o+WvBbSifWFThBXLP7BHXGjqYA@mail.gmail.com \
    --to=justin@dslr.net \
    --cc=bloat@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