search for: pipe1

...Ps are really mean/useless and wont let you send from you own addresses if you dont lease them from the ISP. boo. this will ofcourse still bring the content all down one pipe still... upstream load balancing restored, downstream still skewed.... OR break the clients into two groups, those using pipe1 by default, those using pipe2 by default when talking to MSN. As long as both connextions stay up no one complains, if one goes down, half of them complain ''i got logged off''. Im sure you can rig a proxy on each upstream feed that conducts the signin process for them everytim...

...ts, a list of pipeline stages and a list of operand latencies. The latency of an instruction is captured by the latency of its "definition" operands, so latency does not need to be modeled in the pipeline stages at all. A 2 wide, 1 deep pipeline (2x1) would be: [InstrStage<1, [Pipe0, Pipe1]>] A 2 wide, 4 deep pipeline (2x4) would be: [InstrStage<1, [Pipe0, Pipe1]>] Surprise. There is no difference in the pipeline description, because the units are fully pipelined and we don't need to express latency here. (I'm only showing the pipeline stages here, not the operand...

...ource netmasks NOPRIOHOSTSRC= # low priority destination netmasks NOPRIOHOSTDST= # low priority source ports NOPRIOPORTSRC= # low priority destination ports NOPRIOPORTDST= # Now remove the following two lines :-) #echo Please read the documentation in ''README'' first #exit #pipe1 if [ "$1" = "status" ] then tc -s qdisc ls dev $DEV tc -s class ls dev $DEV exit fi # clean existing down- and uplink qdiscs, hide errors tc qdisc del dev $DEV root 2> /dev/null > /dev/null tc qdisc del dev $DEV ingress 2> /dev/null > /dev/null...