From: Ingo Molnar <mingo@elte.hu>
To: "Török Edvin" <edwintorok@gmail.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: CFS Scheduler and real-time tasks
Date: Thu, 17 May 2007 21:23:43 +0200 [thread overview]
Message-ID: <20070517192343.GA24249@elte.hu> (raw)
In-Reply-To: <4354d3270705171214v25bc4834t5e28a08649761e91@mail.gmail.com>
* Török Edvin <edwintorok@gmail.com> wrote:
> Is there something I am doing wrong, or is the precision decrease
> expected, when running real-time tasks too?
yeah: real-time tasks are ueber-tasks that just get all CPU time
immediately. I guess we could make SCHED_RR be covered by CFS accounting
eventually.
> Very precise indeed, the default scheduler produces lots of different
> timings there.
note: you ran it on a dual-core system and the SMP load-balancer needs
time to gain precision in the non-RT test - so i'd suggest to test it
much longer than 10 seconds: 300 seconds at least.
Ingo
next prev parent reply other threads:[~2007-05-17 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 19:14 CFS Scheduler and real-time tasks Török Edvin
2007-05-17 19:23 ` Ingo Molnar [this message]
2007-05-17 20:10 ` Török Edvin
2007-05-17 20:13 ` Ingo Molnar
2007-05-18 21:07 ` Török Edvin
2007-06-16 7:21 ` Török Edvin
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=20070517192343.GA24249@elte.hu \
--to=mingo@elte.hu \
--cc=edwintorok@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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