netdev - Re: netem and hierarchical ingress traffic shaping

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111218115549.0d9e1259@nehalam.linuxnetplumber.net>
Date:	Sun, 18 Dec 2011 11:55:49 -0800
From:	Stephen Hemminger <shemminger@...tta.com>
To:	"John A. Sullivan III" <jsullivan@...nsourcedevel.com>
Cc:	netdev@...r.kernel.org
Subject: Re: netem and hierarchical ingress traffic shaping

On Sun, 18 Dec 2011 00:12:12 -0500
"John A. Sullivan III" <jsullivan@...nsourcedevel.com> wrote:

> Since netem appears to be classless, we realized we would need to
> replace the SFQ on each leaf with netem which we really didn't want to
> do - not only to not lose SFQ but because we didn't want to maintain the
> netem parameters on each leaf.  So, we activated our ifb1 interface,
> placed netem on it and redirected all the egress traffic to ifb1.  Taht
> worked fine.

Current versions of netem can take one class.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html