From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: Blue and SFB
Date: Thu, 04 Mar 2004 14:05:57 +0000 [thread overview]
Message-ID: <404737C5.9000505@trash.net> (raw)
In-Reply-To: <87ishkzpf5.fsf@iki.fi>
Nuutti Kotivuori wrote:
> Patrick McHardy wrote:
>
>>There is a blue implementation for Linux at
>>http://home.sch.bme.hu/~bartoki/projects/thesis/2001-May-26/
>
>
> Nice!
>
> I briefly scanned the implementation and it didn't look too bad. Some
> oddities here and there (such as changing HZ from 100 to 1024??).
Yes, it seems to be in a good form. The HZ change doesn't make much
sense for a work-conserving scheduler, the PSCHED_CLOCK_SOURCE
change is there to get a higher clock resolution.
> 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 couldn't sleep this morning so I started to fix up the code for 2.6 ;)
It's almost no work, the QoS-subsystem hasn't changed much since 2.4.3.
I should be done today or tommorrow.
> What is the process of getting new traffic schedulers in the kernel? I
> guess most of the netfilter stuff goes through netfilter development
> and patch-o-matic - but there isn't anything similar for QoS, is
> there?
No, there isn't. The usual way it to submit new stuff to netdev
for discussion, if it is useful and of good quality it usually is
accepted.
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-04 14:05 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 [this message]
2004-03-06 15:09 ` Patrick McHardy
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=404737C5.9000505@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.