Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Eric Johansson <esj@eggo.org>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] trying to make sense of what switch vendors say wrt buffer bloat
Date: Tue, 7 Jun 2016 13:51:00 -0400	[thread overview]
Message-ID: <a375d35c-0a88-97b1-0ffd-72d51134b3d0@eggo.org> (raw)
In-Reply-To: <1465268329.938313737@apps.rackspace.com>

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



On 6/6/2016 10:58 PM, dpreed@reed.com wrote:
>
> Even better, it would be fun to get access to an Arista switch and
> some high performance TCP sources and sinks, and demonstrate extreme
> bufferbloat compared to a small-buffer switch.  Just a demo, not a
> simulation full of assumptions and guesses.
>

I'm in the middle of a server room/company move.  I can make a available
a  XSM4348S NETGEAR M4300-24X24F, and probably an arista 7050T-52 for a
short time frame as part of my "testing".  tell me what you need for a
test setup, give me a script I can run and where I should send the
results.  I really need a cut and paste test because I have no time to
think about anything more than the move.

thanks.


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

  parent reply	other threads:[~2016-06-07 17:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 15:29 Eric Johansson
2016-06-06 16:53 ` Toke Høiland-Jørgensen
2016-06-06 17:46   ` Jonathan Morton
2016-06-06 18:37     ` Mikael Abrahamsson
2016-06-06 21:16       ` Ketan Kulkarni
2016-06-07  2:52         ` dpreed
2016-06-07  2:58           ` dpreed
2016-06-07 10:46             ` Mikael Abrahamsson
2016-06-07 14:46               ` Dave Taht
2016-06-07 17:51             ` Eric Johansson [this message]
2016-06-10 21:45               ` dpreed
2016-06-11  1:36                 ` Jonathan Morton
2016-06-11  8:25                 ` Sebastian Moeller
2021-07-02 16:42           ` [Cerowrt-devel] Bechtolschiem Dave Taht
2021-07-02 16:59             ` [Cerowrt-devel] [Bloat] Bechtolschiem Stephen Hemminger
2021-07-02 19:46               ` Matt Mathis
2021-07-07 22:19                 ` [Cerowrt-devel] Abandoning Window-based CC Considered Harmful (was Re: [Bloat] Bechtolschiem) Bless, Roland (TM)
2021-07-07 22:38                   ` Matt Mathis
2021-07-08 11:24                     ` [Cerowrt-devel] " Bless, Roland (TM)
2021-07-08 13:29                       ` Matt Mathis
2021-07-08 14:05                         ` [Cerowrt-devel] " Bless, Roland (TM)
2021-07-08 14:40                         ` [Cerowrt-devel] [Bloat] Abandoning Window-based CC Considered Harmful (was Bechtolschiem) Jonathan Morton
2021-07-08 20:14                           ` David P. Reed
2021-07-08 13:29                       ` Neal Cardwell
2021-07-02 20:28               ` [Cerowrt-devel] [Bloat] Bechtolschiem Jonathan Morton
2016-06-07 22:31 ` [Cerowrt-devel] trying to make sense of what switch vendors say wrt buffer bloat Valdis.Kletnieks

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a375d35c-0a88-97b1-0ffd-72d51134b3d0@eggo.org \
    --to=esj@eggo.org \
    --cc=cerowrt-devel@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