On Sat, Apr 15, 2000 at 07:54:50PM +0200, [EMAIL PROTECTED] wrote:
> Hello!
>
> > Maybe it would be really best to kill this buggy peace of code and replace
> > it with backlog RED (which would fit much better in the normal framework)
>
> I tried RED in 2.3. It does not change anything, at least
> I did not find parameters, when it behaves better than tail drop.
>
> My interpretation was that RED is useful only for "elastic" streams,
> when offender reacts to dropping with a backoff. SYN stream is never
> elastic, hence RED is equivalent to tail drop not depending on
> parameters. But this reasoning may be wrong. The only truth is that
> RED is not so easy to tune. 8)
Hmm, that's bad news. I thought the BSD guys had good experience with RED
syndrop.
I was planning to use RED to make the memory management for the defragment
code better. Especially with always defrag the current algorithm is not
very good and can be easily DOSed - unfortunately a lot of people use that
on their firewalls. I'll do some experiments next week.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
