All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Kalmer <kenneth.kalmer@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] wrr in 2.6.x
Date: Mon, 30 May 2005 14:14:33 +0000	[thread overview]
Message-ID: <fad9d48405053007141d903f57@mail.gmail.com> (raw)
In-Reply-To: <fad9d4840505300559607e95ae@mail.gmail.com>

On 5/30/05, Evgeni Gechev <etg@setcom.bg> wrote:
> Kenneth Kalmer wrote:
> 
> >Guys
> >
> >Given the replies and interests lately on the WRR scheduler, and the
> >shameless promotion of Route Hat (only kidding), my question is
> >simple. Is there an alternative for the 2.6.x kernels?
> >
> >>From what I gather WRR is only available for the 2.4 kernels...
> >
> >Regards
> >
> >
> >
> http://www.zz9.dk/wrr
> 

You're a legend, thanks!

-- 

Kenneth Kalmer
kenneth.kalmer@gmail.com
http://opensourcery.blogspot.com
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2005-05-30 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-30 12:59 [LARTC] wrr in 2.6.x Kenneth Kalmer
2005-05-30 13:29 ` Evgeni Gechev
2005-05-30 14:14 ` Kenneth Kalmer [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=fad9d48405053007141d903f57@mail.gmail.com \
    --to=kenneth.kalmer@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 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.