All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Lost packets and strange "behaviour" of my TC rules
Date: Mon, 17 Oct 2005 21:29:12 +0000	[thread overview]
Message-ID: <435417A8.4020705@dsl.pipex.com> (raw)
In-Reply-To: <BAY107-F75F42364D6EC6123176BBC67F0@phx.gbl>

Paulo Augusto wrote:


> 
> I'm using the TG (www.postel.org/tg <http://www.postel.org/tg>) as a TCP traffic 
> generator, to establish three 90kbits/s TCP flows from PC1(any port) to PC2(port 
> 20000, 20001 and 20002), with different durations and pause times, which as can 
> be shown in the next files:

Usually tcp won't be like this, netperf may be better to test with, as 
it's more normal for bulk tcp to try to go as fast as it can.

> 
> I've also plotted a graph with gnuplot, showing me that (somehow) my rules were 
> "correct", I've got an average value of 30kbits/s, a 10kbits/s and a 60kbits/s.
> 
> Is it normal that some packets get dropped by the rules or not (taking into 
> account my test configuration) ?

The packets are not dropped in this case as the default queue length for 
sfq is 128, which can hold a rwin worth of data. The missing packets 
just didn't get sent because htb slowed the packets down to the rates 
specified and the sender will only send more once the ones already sent 
are acked.

Andy.

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2005-10-17 21:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-16 21:15 [LARTC] Lost packets and strange "behaviour" of my TC rules Paulo Augusto
2005-10-17 21:29 ` Andy Furniss [this message]
2005-10-23 20:09 ` Paulo Augusto

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=435417A8.4020705@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --cc=lartc@vger.kernel.org \
    /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.