From: "Roy" <roy@xxx.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] [ANNOUNCE] sch_dup - duplicate packet queue discipline [2.6]
Date: Mon, 29 Mar 2004 18:30:46 +0000 [thread overview]
Message-ID: <010501c415bb$f8f7e600$030aa8c0@t> (raw)
In-Reply-To: <Pine.LNX.4.58.0403291625230.13656@hosting.rdsbv.ro>
Where such thing can be used?
and why you implemented such thing as sheduler, not iptables module?
> This is my first work for kernel, so please have mercy. :)
>
> OK, I like to announce sch_dup, a new queue discipline that, attached to a
> class (or a device, as root) duplicate packets that pass. Yes, you can
> control the frequency of duplicates.
>
> Example:
> tc qdisc add dev eth0 root dup limit 100 gap 1
> This means: create a pfifo queue and send packets with
> a gap of 1 (0 = no dups) between duplicates:
> gap=0: no duplication
> gap=1: NDNDNDNDND
> gap=2: NNDNNDNNDNNDNND
> (N=not duplicated, D duplicated)
>
> Attached are 3 patches: 1 patch for net/sched dir, other
> for include/linux/pkg_sched.h, and the last for iproute2.
>
> Any comments are appreciated.
>
> David, please include it in 2.6.
> Alexey, please include the third patch in iproute2.
>
> Thank you!
> ---
> Catalin(ux aka Dino) BOIE
> catab at deuroconsult.ro
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-03-29 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 13:45 [LARTC] [ANNOUNCE] sch_dup - duplicate packet queue discipline [2.6] Catalin BOIE
2004-03-29 13:45 ` Catalin BOIE
2004-03-29 18:30 ` Roy [this message]
2004-03-30 6:00 ` [LARTC] [ANNOUNCE] sch_dup - duplicate packet queue discipline Catalin BOIE
2004-03-30 12:29 ` [LARTC] [ANNOUNCE] sch_dup - duplicate packet queue discipline [2.6] Roy
2004-03-30 12:48 ` [LARTC] [ANNOUNCE] sch_dup - duplicate packet queue discipline 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='010501c415bb$f8f7e600$030aa8c0@t' \
--to=roy@xxx.lt \
--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.