From: yoyo <adrian.vasile@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] hfsc scheduler
Date: Fri, 29 Oct 2004 23:39:37 +0000 [thread overview]
Message-ID: <2f6c0cb2041029163944829e6d@mail.gmail.com> (raw)
In-Reply-To: <2f6c0cb2041029160678a8894b@mail.gmail.com>
i remember on this list someone tried hfsc (he had some nice
comparison graphs between hfsc&htb) but i can't seem to find the
message in the archives.. :(
On Fri, 29 Oct 2004 23:33:25 +0000, yoyo <adrian.vasile@gmail.com> wrote:
> me too :)
>
>
>
>
> On Fri, 29 Oct 2004 19:20:35 -0400, Jason Boxman <jasonb@edseek.com> wrote:
> > On Friday 29 October 2004 19:06, yoyo wrote:
> > > hi all,
> > >
> > > long time since i posted on the list.
> > > just wondering if anybody has played around with hfsc and if so could
> > > he/she share their info on it
> >
> > http://www-2.cs.cmu.edu/afs/cs.cmu.edu/user/hzhang/WWW/HFSC/
> > http://www.tik.ee.ethz.ch/~crossbow/rp/plugins/hfsc.html
> > http://trash.net/~kaber/hfsc/
> >
> > I'd be curious to see actual examples of usage, though.
> >
> > --
> >
> > 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/
> >
>
> --
> To mess up a Linux box, you need to work at it; to mess up your Windows
> box, you just need to work on it.
>
--
To mess up a Linux box, you need to work at it; to mess up your Windows
box, you just need to work on it.
_______________________________________________
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-10-29 23:39 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 [this message]
2004-10-30 0:03 ` Andy Furniss
2004-11-01 12:46 ` syrius.ml
2004-11-02 3:18 ` Jason Boxman
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=2f6c0cb2041029163944829e6d@mail.gmail.com \
--to=adrian.vasile@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox