From: Jason Boxman <jasonb@edseek.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] hfsc scheduler
Date: Tue, 02 Nov 2004 03:18:03 +0000 [thread overview]
Message-ID: <200411012218.03506.jasonb@edseek.com> (raw)
In-Reply-To: <2f6c0cb2041029160678a8894b@mail.gmail.com>
On Monday 01 November 2004 07:46, syrius.ml@no-log.org wrote:
<snip>
> My interactive class is defined like this:
> ... ls umax ${MTU}b dmax 25ms rate ${MAX}kbit \
> rt umax ${MTU}b dmax 25ms rate ${MAX}kbit
Where is the 'ls', 'rt', and the other parameters explained? I'm guessing
'rt' is realtime? What's 'ls'?
<snip>
> I'm pretty sure a howto-use-hfsc-in-real-context+faq could help. :)
> unfortunatly I'm afraid not a lot of people can write it :)
> i've read the theory docs, english isn't not my monther tongue language
> and for me there's a huge gap between hfsc theory and hfsc in a real
> situation.
I think I understand what hfsc is attempting to address, but it's never been
made clear how exactly you interact with Linux's hfsc implementation via the
`tc` binary.
--
Jason Boxman
Perl Programmer / *NIX Systems Administrator
Shimberg Center for Affordable Housing | University of Florida
http://edseek.com/ - Linux and FOSS stuff
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-11-02 3:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 23:06 [LARTC] hfsc scheduler yoyo
2004-10-29 23:20 ` Jason Boxman
2004-10-29 23:39 ` yoyo
2004-10-30 0:03 ` Andy Furniss
2004-11-01 12:46 ` syrius.ml
2004-11-02 3:18 ` Jason Boxman [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=200411012218.03506.jasonb@edseek.com \
--to=jasonb@edseek.com \
--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.