From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: Blue and SFB
Date: Sat, 06 Mar 2004 15:09:19 +0000 [thread overview]
Message-ID: <4049E99F.3080605@trash.net> (raw)
In-Reply-To: <87ishkzpf5.fsf@iki.fi>
> Nuutti Kotivuori wrote:
>> But, as the implementation is rather old, it would require a complete
>> overhaul for 2.6 I think. It is a shame it wasn't worked in to the
>> Linux kernel when it was still current, as I think the algorithm could
>> have a lot of uses.
>
I've completed the port and tested it yesterday, unfortunately it's
not useable in the real world as is. There is a strong bias against
non-ECN flows because their packets are simply dropped instead of
marked. At high load (50 ECN vs. 1 non-ECN flow) and a marking
probability of about 10% the non-ECN flow simply stalls.
I can send you the patch if you're interested ..
Regards
Patrick
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-03-06 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 13:56 [LARTC] Re: Blue and SFB Nuutti Kotivuori
2004-03-04 14:05 ` Patrick McHardy
2004-03-06 15:09 ` Patrick McHardy [this message]
2004-03-06 15:33 ` Nuutti Kotivuori
2004-03-06 15:59 ` Patrick McHardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4049E99F.3080605@trash.net \
--to=kaber@trash.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox