Re: [RFC] iproute2/tc caching proposal

[Jarek Poplawski <jarkao2@gmail.com>]

On Thu, May 07, 2009 at 10:49:27PM +0300, Denys Fedoryschenko wrote:
> On Thursday 07 May 2009 22:27:02 Jarek Poplawski wrote:
> > Jarek Poplawski wrote, On 05/07/2009 08:44 PM:
> > > Do you mean 30 sec. is to short for a change? I don't know these things
> > > enough; your idea looks very nice, but I wonder if you tested how it
> > > behaves if e.g. after 15k rules some dev goes away which is used in the
> > > next 15k?
> >
> > Hmm... actually, it seems there should be no problem, except less info on
> > the
> >
> > reason of the failure.
> Info will be same, completely. Just case with changing interfaces have to be 

If a device was removed you wouldn't get e.g. "Cannot find device ..."
from mirred, I guess.

> handled correctly in any case, in case of batch. It is difficult to explain, 
> each person doing his own way shapers. I can explain even, why in my case 
> caching is better. And probably all other, properly done shapers for such 
> cases.
> 
> But for me critical, that when i load shaper, machine is for 10 minutes eating 
> dust (cpu utilisation is high, fans turning like hell :-))) ), and some of 
> users have bandwidth without restrictions. 30 secs much better, and still 
> here is space for improvement.

I agree the gains look very atractive here.

Jarek P.