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 for Android: free password hash cracker in your pocket

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

Message-Id: <20111223.143653.1443323405556018049.davem@davemloft.net>
Date:	Fri, 23 Dec 2011 14:36:53 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	shemminger@...tta.com
Cc:	eric.dumazet@...il.com, dave.taht@...il.com,
	jsullivan@...nsourcedevel.com, netdev@...r.kernel.org
Subject: Re: netem and hierarchical ingress traffic shaping

From: Stephen Hemminger <shemminger@...tta.com>
Date: Fri, 23 Dec 2011 11:07:49 -0800

> So basically, netem, choke, and sfb are incompatible with
> each other. This is not that bad, why not add a flag to qdisc
> ops to indicate which qdisc are using cb and block user from
> trying to do something bogus.

Or we could do what we do in the inet stack, define a layout
that allows the different layers to use different parts of the
CB.
--
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