public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhltc@us.ibm.com>
To: Sitsofe Wheeler <sitsofe@yahoo.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, 06 Mar 2009 16:17:47 -0800	[thread overview]
Message-ID: <49B1BD2B.1040500@us.ibm.com> (raw)
In-Reply-To: <20090306230804.GA963@silver.sucs.org>

Sitsofe Wheeler wrote:
> 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...

Right, excellent point.  Regardless of how thing are right now, relying 
on the kernel revision is a bad idea for this reason.

-- 
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team

      reply	other threads:[~2009-03-07  0:18 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
2009-03-07  0:17       ` Darren Hart [this message]

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=49B1BD2B.1040500@us.ibm.com \
    --to=dvhltc@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=sitsofe@yahoo.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