From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Thomas Graf <tgraf@suug.ch>, Asim Shankar <asimshankar@gmail.com>,
netdev@oss.sgi.com
Subject: Re: SFQ: Reordering?
Date: Tue, 10 May 2005 00:14:47 +0100 [thread overview]
Message-ID: <427FEEE7.2040104@dsl.pipex.com> (raw)
In-Reply-To: <427C19C3.5030304@trash.net>
Patrick McHardy wrote:
> It would be interesting to see this in real-life, when a single flow
> is hashed to multiple buckets (it can be even more than two) and
> each bucket has some packets queued, the result should look pretty
> chaotic.
It certainly hurts latency if used for ingress shaping, perturb nearly
always makes the sender backoff and then burst.
Andy.
prev parent reply other threads:[~2005-05-09 23:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 21:53 SFQ: Reordering? Asim Shankar
2005-05-06 22:07 ` Patrick McHardy
2005-05-06 22:46 ` Patrick McHardy
2005-05-06 23:02 ` Thomas Graf
2005-05-06 23:19 ` Patrick McHardy
2005-05-07 0:58 ` Thomas Graf
2005-05-07 1:28 ` Patrick McHardy
2005-05-08 11:51 ` Thomas Graf
2005-05-08 16:03 ` Patrick McHardy
2005-05-08 18:33 ` Thomas Graf
2005-05-09 23:14 ` Andy Furniss [this message]
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=427FEEE7.2040104@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=asimshankar@gmail.com \
--cc=kaber@trash.net \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
/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.