From: Jamie Lokier <jamie@shareable.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Miguel Freitas <miguel@cetuc.puc-rio.br>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] SCHED_SOFTRR linux scheduler policy ...
Date: Sat, 12 Jul 2003 17:20:29 +0100 [thread overview]
Message-ID: <20030712162029.GE9547@mail.jlokier.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.55.0307120845470.4351@bigblue.dev.mcafeelabs.com>
Davide Libenzi wrote:
> > Cool. What happens if you run two SCHED_SOFTRR tasks and they both
> > use 50% of the CPU - will that starve all the other tasks? Or is the
> > CPU usage of all SOFTRR tasks bounded collectively?
>
> Nope :) They will run their timeslice entirely and then they will try to
> get some more. Looking at their last recharge timestamp, Dad scheduler
> will put them in bed and will give other tasks a chance to run.
Nice, but answer to wrong question, possibly :)
I'm wondering what happens if the tasks are both good, early to bed
without a fuss. Neither runs their entire timeslice.
Or to illustrate: say xine uses 10% of my CPU. What happens when I
open 11 xine windows?
-- Jamie
next prev parent reply other threads:[~2003-07-12 16:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 13:43 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 [this message]
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
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=20030712162029.GE9547@mail.jlokier.co.uk \
--to=jamie@shareable.org \
--cc=davidel@xmailserver.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
all inboxes | Powered by JetHome®