General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave@taht.net>
To: Simon Barber <simon@superduper.net>
Cc: Dave Taht <dave.taht@gmail.com>,  bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] buffer sizing meeting notes
Date: Fri, 23 Aug 2019 10:24:54 -0700	[thread overview]
Message-ID: <87pnkvdcbd.fsf@taht.net> (raw)
In-Reply-To: <42B8EB6B-5540-46EB-8BB3-81D6239A4D58@superduper.net> (Simon Barber's message of "Fri, 23 Aug 2019 10:13:39 -0700")



Simon Barber <simon@superduper.net> writes:

> The Netflix presentation requires a password - can you share it?

I was not at this meeting, I just stumbled across the url. I don't even
know how, I think I was looking for the old (and good!) stanford
buffersizing paper, and there was this set of updates from various
parties on the current state of some hardware.


>
> Simon
>
>
>> On Aug 23, 2019, at 9:07 AM, Dave Taht <dave.taht@gmail.com> wrote:
>> 
>> There's some good preso from various representatives in the dc
>> market here.
>> 
>> The p4 stuff, in particular (from barefoot) is looking impressive.
>> 
>> http://yuba.stanford.edu/~bspang/buffer-sizing-meeting/
>> 
>> 
>> -- 
>> 
>> Dave Täht
>> CTO, TekLibre, LLC
>> http://www.teklibre.com
>> Tel: 1-831-205-9740
>> _______________________________________________
>> 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:[~2019-08-23 17:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23 16:07 Dave Taht
2019-08-23 17:13 ` Simon Barber
2019-08-23 17:24   ` Dave Taht [this message]
2019-08-24  7:54   ` Jesper Dangaard Brouer
2019-08-24  7:59     ` Sebastian Moeller
2019-08-24  9:15       ` Luca Muscariello

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=87pnkvdcbd.fsf@taht.net \
    --to=dave@taht.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=simon@superduper.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