All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Young <tyo@ee.unimelb.edu.au>
To: piet@bluelane.com
Cc: netdev@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: Congestion Avoidance Monitoring Tools
Date: Fri, 21 Apr 2006 15:59:55 +1000	[thread overview]
Message-ID: <1145599196.2534.38.camel@penguin> (raw)
In-Reply-To: <1145597174.12413.17.camel@piet2.bluelane.com>

On Thu, 2006-04-20 at 22:26 -0700, Piet Delaney wrote:
> I'm upgrading our 2.6.12 kernel to 2.6.13, which includes significant
> congestion avoidance code additions and changes. I was wondering if
> there are any tools folks can recommend for testing the kernel to make
> sure the congestion avoidance code is operating correctly. For 
> example the displaying of the congestion window as a function of time
> while undergoing convergence. For causing congestion I could modify 
> a kernel to discard packets once in a while on a lab gateway and hit 
> it with iperf. HP's netperf looks interesting. 
> 
> Any suggestions?
> 
> 
> -piet
> 

Hi,

Try having a look at the output of 'ss -i' (you may need to update to
the latest iproute2 tools). You could either try and parse the text
output of that or use the same inet_diag interface that ss uses to poll
for the data it at regular intervals.

-- 
Thomas Young
http://cubinlab.ee.unimelb.edu.au/~tyo/
Research Assistant
CUBIN Research Centre - University of Melbourne


  reply	other threads:[~2006-04-21  6:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21  5:26 Congestion Avoidance Monitoring Tools Piet Delaney
2006-04-21  5:59 ` Tom Young [this message]
2006-04-21  6:57   ` Andi Kleen
2006-04-21  7:25     ` Piet Delaney
2006-04-21 15:19 ` Stephen Hemminger
2006-04-23 22:52   ` Hagen Paul Pfeifer
2006-04-24 17:39     ` Stephen Hemminger

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

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

  git send-email \
    --in-reply-to=1145599196.2534.38.camel@penguin \
    --to=tyo@ee.unimelb.edu.au \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=piet@bluelane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.