From: "Chris Friesen" <cfriesen@nortel.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: BFS cpu scheduler v0.304 stable release
Date: Fri, 16 Oct 2009 16:53:37 -0600 [thread overview]
Message-ID: <4AD8F971.2090805@nortel.com> (raw)
In-Reply-To: <200910162158.58054.kernel@kolivas.org>
On 10/16/2009 04:58 AM, Con Kolivas wrote:
> to this, BFS also uses sub-tick accounting. What BFS does _not_ now feature is
> support for CGROUPS. The average user should neither need to know what these
> are, nor should they need to be using them to have good desktop behaviour.
That said, it's useful for embedded purposes and I could see some use in
that area for your BFS scheduler since they often care about latency and
tend to use low numbers of cpus.
> It is surprisingly difficult to get accurate CPU accounting, and in many cases,
> the accounting is done by simply determining what is happening at the precise
> moment a timer tick fires off.
With sched_clock() it would seem that this is not as applicable as it
used to be.
Chris
next prev parent reply other threads:[~2009-10-16 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 10:58 BFS cpu scheduler v0.304 stable release Con Kolivas
2009-10-16 22:53 ` Chris Friesen [this message]
2009-10-17 6:44 ` Mike Galbraith
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=4AD8F971.2090805@nortel.com \
--to=cfriesen@nortel.com \
--cc=kernel@kolivas.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.