[LARTC] WonderShaper on LAN link kills to-host speed

[LARTC] WonderShaper on LAN link kills to-host speed

[Kenneth Porter]

I tried installing the WonderShaper on my internal link, mostly to get the
SFQ installed. I set uplink and downlink to 100000 to match the link speed
and changed the bandwidth on the cbq line to 100mbit. This killed transfer
speed *to* the box, knocking it from 30-40 Mbps down to about 800 kbps.
Commenting out just the ingress control restored the speed.

What about the ingress policer would do that?

Here's the effective line after shell expansions:

tc filter add dev eth0 parent ffff: protocol ip prio 50 u32 match ip src \
0.0.0.0/0 police rate 100000kbit burst 10k drop flowid :1

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

Re: [LARTC] WonderShaper on LAN link kills to-host speed

[Stef Coene]

On Tuesday 17 December 2002 23:15, Kenneth Porter wrote:
> I tried installing the WonderShaper on my internal link, mostly to get the
> SFQ installed. I set uplink and downlink to 100000 to match the link speed
> and changed the bandwidth on the cbq line to 100mbit. This killed transfer
> speed *to* the box, knocking it from 30-40 Mbps down to about 800 kbps.
> Commenting out just the ingress control restored the speed.
>
> What about the ingress policer would do that?
I'm not sure, but the policer can calculate the rate in the class in 2 ways.  
And maybe your CPU can't handle the calculations.  What CPU do you have and 
what's the load on the sstem?

> Here's the effective line after shell expansions:
>
> tc filter add dev eth0 parent ffff: protocol ip prio 50 u32 match ip src \
> 0.0.0.0/0 police rate 100000kbit burst 10k drop flowid :1

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

Re: [LARTC] WonderShaper on LAN link kills to-host speed

[Jose Luis Domingo Lopez]

On Tuesday, 17 December 2002, at 14:15:39 -0800,
Kenneth Porter wrote:

> What about the ingress policer would do that?
> 
As far as I know, inbound traffic (ingress) can only police packets,
that is, discard traffic on excess hoping the other end will notice it
and slow down a bit. If you want to classify incoming traffic, create
classes, attach queuing disciplines, and those nice things available in
the outgoing traffic, you must:
a) Patch your kernel with IMQ, redirect incoming traffic to it, and
treat this device as you would any "outgoing" traffic, or...
b) ...manage bandwidth in the outgoing direction on the other network
card attached to the router (if this is a router).

I'm sure somebody in this list can explain himslef much better, and
provide links to information and example code, but hope it helps.

-- 
Jose Luis Domingo Lopez
Linux Registered User #189436     Debian Linux Woody (Linux 2.4.20-xfs)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] WonderShaper on LAN link kills to-host speed

[Kenneth Porter]

--On Wednesday, December 18, 2002 10:43 PM +0100 Stef Coene
<stef.coene@docum.org> wrote:

> I'm not sure, but the policer can calculate the rate in the class in 2
> ways.   And maybe your CPU can't handle the calculations.  What CPU do
> you have and  what's the load on the sstem?

It's a P2-233 with 128 MB memory (Dell PowerEdge 4200). It's a bit
memory-starved but otherwise seems to handle the load. It plays router,
mail server, DNS, and file server. (Long-term plan is to offload
non-gateway functions, once another box is freed up.)

What are the "2 ways"? A pointer to source code would be fine, I just need
to know where to start looking.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] WonderShaper on LAN link kills to-host speed

[Kenneth Porter]

--On Wednesday, December 18, 2002 10:53 PM +0100 Jose Luis Domingo Lopez
<lartc@24x7linux.com> wrote:

> As far as I know, inbound traffic (ingress) can only police packets,
> that is, discard traffic on excess hoping the other end will notice it
> and slow down a bit. If you want to classify incoming traffic

I don't know that I even need the policing function, esp. for LAN traffic
that is only queued at the original sender and in switches. (About 150
clients on a mixed 100/1000 Mbps LAN.) I was just surprised that it killed
traffic so badly. Perhaps I need to read up more on exactly what it's doing.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] WonderShaper on LAN link kills to-host speed

[Stef Coene]

On Wednesday 18 December 2002 23:22, Kenneth Porter wrote:
> --On Wednesday, December 18, 2002 10:43 PM +0100 Stef Coene
>
> <stef.coene@docum.org> wrote:
> > I'm not sure, but the policer can calculate the rate in the class in 2
> > ways.   And maybe your CPU can't handle the calculations.  What CPU do
> > you have and  what's the load on the sstem?
>
> It's a P2-233 with 128 MB memory (Dell PowerEdge 4200). It's a bit
> memory-starved but otherwise seems to handle the load. It plays router,
> mail server, DNS, and file server. (Long-term plan is to offload
> non-gateway functions, once another box is freed up.)
>
> What are the "2 ways"? A pointer to source code would be fine, I just need
> to know where to start looking.
It's in the lartc howto.  You can use a tbf alike function or a rate 
estimator.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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