linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Huey (Hui) <billh@gnuppy.monkey.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Jamie Lokier <jamie@shareable.org>,
	Miguel Freitas <miguel@cetuc.puc-rio.br>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Bill Huey (Hui)" <billh@gnuppy.monkey.org>
Subject: Re: [patch] SCHED_SOFTRR linux scheduler policy ...
Date: Sat, 12 Jul 2003 20:59:18 -0700	[thread overview]
Message-ID: <20030713035918.GA958@gnuppy.monkey.org> (raw)
In-Reply-To: <Pine.LNX.4.55.0307121928540.3528@bigblue.dev.mcafeelabs.com>

On Sat, Jul 12, 2003 at 07:39:25PM -0700, Davide Libenzi wrote:
> This is funny. Every time I found something interesting to read (papers) I
> print them and I stock on my desk. The are 25Kg of papers piled on my desk
> right now. Thanks to you, 25.05Kg now ;) Upon a brief read, The Italian Job,
> hemm ... paper, is very similar to SOFTRR. Once you change their "server"
> notion with the per-user allocation I have in mind, it'll come even
> closer. I really didn't have time to read the MS paper though. The problem
> is not if it can be done, the problem is how bad ppl wants it.

I want it badly, but that's just me. :) The MS is about extending these
concept to apply to SMP resource allocation, which currently isn't something
that these kind of schedulers do. IMO, all of this kind of stuff is going to
be crucial for the next generation of operating systems.  Glue that scheduler
to a thread that's suppose to process network packets/io channels and you'll
have ubiquitous QoS throughout the system directly controllable by the scheduler.

That's my intuition on the subject. Time will tell.

bill


  reply	other threads:[~2003-07-13  3:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-12 13:43 [patch] SCHED_SOFTRR linux scheduler policy Miguel Freitas
2003-07-12 15:20 ` Davide Libenzi
2003-07-12 15:49   ` Jamie Lokier
2003-07-12 15:59     ` Davide Libenzi
2003-07-12 16:20       ` Jamie Lokier
2003-07-12 16:18         ` Davide Libenzi
2003-07-12 16:41         ` Miguel Freitas
2003-07-12 18:51           ` Jamie Lokier
2003-07-13  1:44             ` Davide Libenzi
2003-07-13 14:11               ` Jamie Lokier
2003-07-13 17:15                 ` Davide Libenzi
2003-07-12 22:42       ` Bill Huey
2003-07-13  2:39         ` Davide Libenzi
2003-07-13  3:59           ` Bill Huey [this message]
2003-07-12 16:34   ` Miguel Freitas
2003-07-12 16:30     ` Davide Libenzi
2003-07-12 19:13       ` Miguel Freitas
2003-07-12 20:07         ` Davide Libenzi
2003-07-12 18:44     ` Jamie Lokier
  -- strict thread matches above, loose matches on Subject: below --
2003-07-10  2:33 Davide Libenzi
2003-07-13 11:50 ` Pavel Machek
2003-07-13 11:53   ` Alan Cox
2003-07-13 16:08   ` Davide Libenzi

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=20030713035918.GA958@gnuppy.monkey.org \
    --to=billh@gnuppy.monkey.org \
    --cc=davidel@xmailserver.org \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel@cetuc.puc-rio.br \
    /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;
as well as URLs for NNTP newsgroup(s).