From: Kennedy Cheng <kennedy.cheng@jungle.bt.co.uk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Blue and SFB (Was: how to add my own traffic scheduler to
Date: Thu, 04 Mar 2004 10:51:01 +0000 [thread overview]
Message-ID: <40470A15.BC56C54A@jungle.bt.co.uk> (raw)
In-Reply-To: <878yih1rzw.fsf@iki.fi>
I was not trying to implement the Blue algorithm. It was just a name I
picked as an example. Perhaps I should take a look at Blue as well.
Kennedy
Nuutti Kotivuori wrote:
> Kennedy Cheng wrote:
> > What are the steps needed to add my own traffic scheduler to TC?
>
> >From your small example there, I would guess you are working on a Blue
> scheduler for TC.
>
> Hence I'd like to ask publically from everyone around - has anyone
> seen any efforts to implement Blue[1]? What about SFB, eg. Stochastic
> Fair Blue?
>
> The Blue algorithm seems really straightforward to implement, so I
> really wonder why it hasn't been done already? SFB is ofcourse more
> complex in several ways, but perhaps a lot of code could be reused
> from SFQ, since the basic idea of hashing flows is the same.
>
> Thanks,
> -- Naked
>
> Footnotes:
> [1] http://www.thefengs.com/wuchang/work/blue/
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-03-04 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 22:32 [LARTC] Blue and SFB (Was: how to add my own traffic scheduler to TC) Nuutti Kotivuori
2004-03-04 3:56 ` [LARTC] Blue and SFB (Was: how to add my own traffic scheduler Patrick McHardy
2004-03-04 10:51 ` Kennedy Cheng [this message]
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=40470A15.BC56C54A@jungle.bt.co.uk \
--to=kennedy.cheng@jungle.bt.co.uk \
--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