linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Demo patch - no interactivity 2.6
Date: Wed, 26 Nov 2003 10:59:24 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.58.0311261055280.17204@earth> (raw)
In-Reply-To: <200311241016.08990.kernel@kolivas.org>


On Mon, 24 Nov 2003, Con Kolivas wrote:

> I created this patch for demonstration purposes.
> 
> People have raised concerns about the overhead of the interactivity
> estimator in 2.6 and it's effect on throughput. Some anecdotes report
> wild accusations of 20% loss (without hard data). [...]

this claim is nonsense, agreed. The only small change in performance
should be for microbenchmark things like lmbench's lat_ctx. But this cost
is well worth it.

	Ingo

      reply	other threads:[~2003-11-26 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-23 23:16 Demo patch - no interactivity 2.6 Con Kolivas
2003-11-26  9:59 ` Ingo Molnar [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=Pine.LNX.4.58.0311261055280.17204@earth \
    --to=mingo@elte.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).