LARTC - Mar 2004 - [ANNOUNCE] sch_dup - duplicate packet queue discipline [2.6]

Hello!

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

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/

Hi!
> Where such thing can be used?
Mostly for testing applications and other stuff.
It''s a little bit hard to wait to appear a duplicate so you can test
that
your application works ok.
> and why you implemented such thing as sheduler, not iptables module?
Why iptables module?
Why do you think is better?
>
>
>
> > 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/
>
---
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/

----- Original Message ----- 
From: "Catalin BOIE"
<util@deuroconsult.ro>
> Hi!
>
> > Where such thing can be used?
> Mostly for testing applications and other stuff.
> It''s a little bit hard to wait to appear a duplicate so you can
test that
> your application works ok.
> > and why you implemented such thing as sheduler, not iptables
> module?
> Why iptables module?
> Why do you think is better?
I mean iptables module because it uses iptables hooks, that is most easy way
to control all network trafic.
since this module would not be used very often, you can configure it with
command line on load.


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

> > > and why you implemented such thing as sheduler, not iptables
> > module?
> > Why iptables module?
> > Why do you think is better?
> I mean iptables module because it uses iptables hooks, that is most easy
way
> to control all network trafic.
> since this module would not be used very often, you can configure it with
> command line on load.
I dig a lot in net/sched so this is why I made a queue discipline.
So, no particular reason I didn''t implement it as a netfilter module.

---
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/