[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: BE and EF Isolation



On Wed, 11 Oct 2000, Steve Blake wrote:

> Mariano Korman wrote:
> 
> > >From my own experiments, isolating two traffic classes does not work
> > very well. Nevertheless, there is still a lot of work to do before I can
> > definately sat whether isolating works or not.
> > 
> > regards,
> > 
> >      Mariano Korman
> > 
> > Tan Chee Wei wrote:
> > > 
> > > Hallo,
> > > 
> > > I implemented the example 'efcbq' in the package, iproute2 and observed the
> > > 2 flows, namely BE and EF flows. The EF class is 'isolated' hence by right,
> > > BE is not allowed to borrow bandwidth from EF. However, it is observed that
> > > BE flows ramp up immediately after the EF traffic flow was cut off. Anyone
> > > can offer an explanation? Does that not contradict class isolation ?
> 
> 
> Why would you expect things to behave any differently?  CBQ is work-
> conserving and classes are allowed to borrow bandwidth from other classes
> not fully utilizing their committed share.

	I think you missed the point here.  The class was specified as
'isolated'.  Bandwidth should not be borrowed from isolated classes,
just as bounded classes should not borrow.

---
        The roaches seem to have survived, but they are not routing packets
correctly.
        --About the Internet and nuclear war.