public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Con Kolivas <kernel@kolivas.org>,
	Peter Williams <pwil3058@bigpond.net.au>,
	Andrew Morton <akpm@osdl.org>,
	Nick Piggin <piggin@cyberone.com.au>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Likelihood of rt_tasks
Date: Sat, 10 Jul 2004 22:05:43 +1000	[thread overview]
Message-ID: <40EFDB97.70109@yahoo.com.au> (raw)
In-Reply-To: <20040710111528.GA22265@elte.hu>

Ingo Molnar wrote:

> the unlikely() check in rt_task() was mainly done because there was a
> steady stream of microoptimizations that added unlikely() to rt_task().
> So now we do in everywhere and have removed the unlikely()/likely()
> branches from sched.c. It doesnt really matter in real-world terms, but
> it will make the common case code (non-RT) a tiny bit more compact. And
> i challenge anyone to be able to even measure the difference to an RT
> task.
> 

Also, the scenario where it may possibly make a tiny positive
contribution (something *very* scheduler bound) would be using
non-RT tasks I'd say.

  reply	other threads:[~2004-07-10 12:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-09 10:00 Likelihood of rt_tasks Con Kolivas
2004-07-09 10:17 ` Ingo Molnar
2004-07-09 23:53 ` Peter Williams
2004-07-10  0:16   ` Con Kolivas
2004-07-10  0:41     ` Peter Williams
2004-07-10  0:45       ` Con Kolivas
2004-07-10 11:15     ` Ingo Molnar
2004-07-10 12:05       ` Nick Piggin [this message]
2004-07-10  3:57   ` Elladan
2004-07-10 11:19     ` Ingo Molnar

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=40EFDB97.70109@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=piggin@cyberone.com.au \
    --cc=pwil3058@bigpond.net.au \
    /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