public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <kalin@ThinRope.net>
To: Catalin BOIE <util@deuroconsult.ro>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] sch_ooo - Out-of-order packet queue discipline
Date: Wed, 23 Jun 2004 04:17:04 +0900	[thread overview]
Message-ID: <40D885B0.5080000@ThinRope.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0404021023140.18886@hosting.rdsbv.ro>

Catalin BOIE wrote:
> Hello!
> 
> I like to announce sch_ooo, a new queue discipline that, attached to a
> class (or a device, as root) reorder the packets that pass by delaying 
> some.
> 
> Example:
> tc qdisc add dev eth0 root ooo limit 100 gap 4 wait 1100
> 
> This queue will create a pfifo with limit 100 and will delay
> every 4th packet with 1100ms.
> An stream of 6 packets like this: 1 2 3 4 5 6, generated by
> ping will be reordered like this: 1 2 3 5 4 6.

[snip]

> +config NET_SCH_OOO
> +    tristate "Out-of-order qdisc discipline"
> +    depends on NET_SCHED
> +    help
> +      Say Y if you want to simulate out-of-order packets by delaying
> +      some of them. This qdisc is useful if you develop
> +      protocols or network monitoring applications.

I risk on me:=dumb, but can you give at least one practical application for sch_ooo?
I suppose you have something on your mind...

Kalin.

-- 
||///_ o  *****************************
||//'_/>     WWW: http://ThinRope.net/


  parent reply	other threads:[~2004-06-22 19:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22 13:15 [ANNOUNCE] sch_ooo - Out-of-order packet queue discipline Catalin BOIE
2004-06-22 15:46 ` [LARTC] " Stephen Hemminger
2004-06-22 17:52   ` Catalin BOIE
2004-06-22 20:14     ` David S. Miller
2004-06-22 19:17 ` Kalin KOZHUHAROV [this message]
2004-06-23  5:32   ` Catalin BOIE

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=40D885B0.5080000@ThinRope.net \
    --to=kalin@thinrope.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=util@deuroconsult.ro \
    /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