Thanks very much! One quick kernel upgrade later (to add fq_codel support)
and that has definitely helped. I'll run a larger set of tests and report
back.
One final question: I understand that this applies a 100Mbit aggregate
shaper to the specified destination(s). I'd like to instead apply this
shaper on a per-destination or per-flow basis, but without specifying each
individual destination (i.e. so that 10x 100M clients could still saturate
the 1G link). Do you know if this is possible?
Thanks,
Sam
On 9 July 2013 16:27, Eric Dumazet <eric.duma...@gmail.com> wrote:
> On Tue, 2013-07-09 at 15:53 +0100, Sam Crawford wrote:
>
> >
> > I've tried dropping the qlen down (even to zero), but to no effect. Is
> > this still expected? I've got total control over both client and
> > server components, so can change pretty much anything to improve
> > matters.
>
> As the bottleneck is not at the sender, you have no queueing on it, so
> qlen has absolutely no effect.
>
> Thats why you should create the bottleneck on the sender, to properly
> control it.
>
> This script would be a start :
>
> ETH=eth0
> EST="est 1sec 4sec"
> REMOTE_WAN_NET=192.168.9/24
>
> tc qd del dev $ETH root 2>/dev/null
>
> tc qdisc add dev $ETH root handle 1: $EST htb r2q 1000 default 2
> tc class add dev $ETH parent 1: classid 1:1 $EST htb rate 100Mbit
>
> tc qdisc add dev $ETH parent 1:1 handle 10: $EST fq_codel
>
> filter add dev $ETH parent 1: protocol ip u32 \
> match ip dst $REMOTE_WAN_NET flowid 1:1
>
>
>
>
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired