From: Miguel Freitas <miguel@cetuc.puc-rio.br>
To: Jamie Lokier <jamie@shareable.org>
Cc: Davide Libenzi <davidel@xmailserver.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] SCHED_SOFTRR linux scheduler policy ...
Date: 12 Jul 2003 13:41:04 -0300 [thread overview]
Message-ID: <1058028064.1196.111.camel@mf> (raw)
In-Reply-To: <20030712162029.GE9547@mail.jlokier.co.uk>
On Sat, 2003-07-12 at 13:20, Jamie Lokier wrote:
> 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?
well of course 110% is more than what you have of resources and xine
would have to drop frames to keep it up... :)
anyway, if xine uses 10% of your CPU, that time is mostly likely spent
at the decoder thread. the only thread that i would set to use SOFTRR
would be the output thread, which does use very like CPU.
regards,
Miguel
next prev parent reply other threads:[~2003-07-12 16:21 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 [this message]
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=1058028064.1196.111.camel@mf \
--to=miguel@cetuc.puc-rio.br \
--cc=davidel@xmailserver.org \
--cc=jamie@shareable.org \
--cc=linux-kernel@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.