Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Brian Trammell <ietf@trammell.ch>, "aqm@ietf.org" <aqm@ietf.org>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"
Date: Tue, 03 Mar 2015 01:45:25 -0500	[thread overview]
Message-ID: <34374.1425365125@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 02 Mar 2015 11:17:33 +0100." <alpine.DEB.2.02.1503021108270.20507@uplift.swm.pp.se>

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

On Mon, 02 Mar 2015 11:17:33 +0100, Mikael Abrahamsson said:

> We have a huge amount of information in our TCP stacks that either are
> locked in there and not used properly to help users figure out what's
> going on, and there is basically zero information flow between the
> applications using TCP and the TCP stack itself. Each just tries to do its
> best on its own layer.

You might want to touch base with the 'web10g' crew, who are working on
instrumenting the Linux network stack to expose more of the inner variables
for analysis and tuning.

http://web10g.org/

[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

  parent reply	other threads:[~2015-03-03  6:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02  3:57 [Cerowrt-devel] " Dave Taht
2015-03-02  4:00 ` [Cerowrt-devel] [aqm] " Andrew Mcgregor
2015-03-02  4:05 ` Mikael Abrahamsson
2015-03-02  4:06 ` [Cerowrt-devel] " David Lang
2015-03-02  9:40 ` [Cerowrt-devel] [aqm] " Brian Trammell
2015-03-02 10:17   ` Mikael Abrahamsson
2015-03-02 10:54     ` [Cerowrt-devel] [Bloat] " Jonathan Morton
2015-03-02 12:44       ` dpreed
2015-03-02 14:45       ` Brian Trammell
2015-03-02 18:41         ` David Lang
2015-03-03  6:45     ` Valdis.Kletnieks [this message]
2015-03-04  8:14       ` [Cerowrt-devel] " Mikael Abrahamsson
2015-03-02 21:53   ` Joe Touch
2015-03-02 23:14     ` David Lang
2015-03-02 23:25       ` Joe Touch
2015-03-02 23:34         ` David Lang
2015-03-03  0:07           ` Andrew Mcgregor
2015-03-02 10:47 ` Dave Dolson
2015-03-02 10:49   ` Andrew Mcgregor
2015-03-02 18:36     ` David Lang
     [not found] ` <md2fsa$o1s$1@ger.gmane.org>
2015-03-02 20:33   ` Dave Dolson
2015-03-02 20:39     ` David Lang
2015-03-02 20:38   ` Dave Taht
2015-03-04  8:12     ` Mikael Abrahamsson
2015-03-03 17:20 ` Fred Baker (fred)
2015-03-03 17:29   ` [Cerowrt-devel] [Bloat] " Wesley Eddy
2015-03-03 18:00     ` [Cerowrt-devel] [aqm] [Bloat] " Fred Baker (fred)
2015-03-04  5:24       ` Dave Taht
2015-03-05 18:56         ` Curtis Villamizar
2015-03-05 19:50           ` [Cerowrt-devel] [Bloat] [aqm] " Rich Brown
2015-03-04 17:34       ` [Cerowrt-devel] [aqm] [Bloat] " dpreed
2015-03-04 19:45         ` Mikael Abrahamsson
2015-03-05 20:38 ` [Cerowrt-devel] " Matt Taggart
2015-03-05 20:53   ` Dave Taht

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=34374.1425365125@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=ietf@trammell.ch \
    --cc=swmike@swm.pp.se \
    /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