From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Darren Hart <dvhltc@us.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
"lkml, " <linux-kernel@vger.kernel.org>
Subject: Re: Dynamically determine if kernel includes CFS Scheduler
Date: Fri, 6 Mar 2009 23:08:04 +0000 [thread overview]
Message-ID: <20090306230804.GA963@silver.sucs.org> (raw)
In-Reply-To: <49B1AB3A.2050303@us.ibm.com>
On Fri, Mar 06, 2009 at 03:01:14PM -0800, Darren Hart wrote:
>
> So I am of course in agreement with both you and Peter. In this case,
> the development team of an existing product is trying to move away from
> heavy use of sched_yield(), and the CFS scheduler provides some
Hmm. The only thing I'll say about checking kernel versions is: do some
tests/checks with the different enterprise distro kernels. I don't think
they tend to do big backports any more but if they have that kernel
version check could become tricky...
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2009-03-06 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 20:44 Dynamically determine if kernel includes CFS Scheduler Darren Hart
2009-03-06 21:01 ` Peter Zijlstra
2009-03-06 22:53 ` Sitsofe Wheeler
2009-03-06 23:01 ` Darren Hart
2009-03-06 23:08 ` Sitsofe Wheeler [this message]
2009-03-07 0:17 ` Darren Hart
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=20090306230804.GA963@silver.sucs.org \
--to=sitsofe@yahoo.com \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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.