* Alexey Kuznetsov ([EMAIL PROTECTED]) wrote:
> Hello!
>
> > Thanks for that explanation - it helps somewhat - one thing I was
> > confused by was why the timer mechanism for the garbage collection
> > was so elaborate; why does it do all that back off stuff and
> > adjusting itself? Why not just
Hello!
> Thanks for that explanation - it helps somewhat - one thing I was
> confused by was why the timer mechanism for the garbage collection
> was so elaborate; why does it do all that back off stuff and
> adjusting itself? Why not just run at some fixed rate?
What's about timer in dst.c, it i
Hi,
Alexey and Herbert - thanks for the replies.
Alexey wrote:
> > similar things on a router - it has died 3 or 4 times (over a period
> > of a few months) with such an error with very little traffic passing
> > through it and a stream of the 'dst cache overflow' errors on the screen.
>
> Act
Alexey Kuznetsov <[EMAIL PROTECTED]> wrote:
>
> Really bad overflow happens when lots of entries remain in use, because
> someone forgot to release the references to dst cache entries.
> It is the first thing to check.
Yes. I once had a situation where a buggy user-land program held
many sockets
Hello!
> similar things on a router - it has died 3 or 4 times (over a period
> of a few months) with such an error with very little traffic passing
> through it and a stream of the 'dst cache overflow' errors on the screen.
Actually, it is quite unusual. The problems with garbage collection
are
Hi,
I noticed a discussion on netdev
with someone getting dst cache overflow errors; I've been experiencing
similar things on a router - it has died 3 or 4 times (over a period
of a few months) with such an error with very little traffic passing
through it and a stream of the 'dst cache overflow'
