public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [2.6.16-rc6 patch] remove sleep_avg multiplier
Date: Tue, 14 Mar 2006 13:59:55 +0100	[thread overview]
Message-ID: <1142341195.11303.31.camel@homer> (raw)
In-Reply-To: <200603142347.19927.kernel@kolivas.org>

On Tue, 2006-03-14 at 23:47 +1100, Con Kolivas wrote:
> On Tuesday 14 March 2006 23:40, Mike Galbraith wrote:
> > On Tue, 2006-03-14 at 23:29 +1100, Con Kolivas wrote:
> > > On Tuesday 14 March 2006 23:24, Mike Galbraith wrote:
> > > > Don't forget, every one of the exploits I test with were posted by
> > > > people who were experiencing scheduler problems in real life.  Try to
> > > > use your box while running those exploits, and then tell me that you
> > > > agree with interbench's assessment.
> > >
> > > Ok you feel interbench is an irrelevant benchmark for your test case and
> > > I'm not going to bother arguing since it doesn't claim to test every
> > > single situation.
> >
> > Yes.  Interbench's opinion is irrelevant to me wrt this problem.
> 
> Ok one last try to explain where I'm coming from and then I'll give up ...
> 
> Interbench's opinion is not irrelevant to me on this because it may help your 
> nfs case but interbench does tell me what happens with X, video, audio etc. 
> It's precisely because it quantifies those other scenarios that I care.

Sure, and I'm not trying to knock interbench.  I used it as yet another
test to my changes as I made them.  I just disagree with it's opinion.

(I didn't misunderstand the code either, I observed it in action,
interpreted the difference between reaction to stock, and reaction to my
changes, and then went straight to the long sleep logic and [tweak] made
the numbers identical to guarantee that I understood)

	-Mike


      reply	other threads:[~2006-03-14 12:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14  9:51 [2.6.16-rc6 patch] remove sleep_avg multiplier Mike Galbraith
2006-03-14  9:56 ` Ingo Molnar
2006-03-14 10:05   ` Con Kolivas
2006-03-14 10:10     ` Con Kolivas
2006-03-14 11:56       ` Mike Galbraith
2006-03-14 12:07         ` Con Kolivas
2006-03-14 12:24           ` Mike Galbraith
2006-03-14 12:29             ` Con Kolivas
2006-03-14 12:36               ` Con Kolivas
2006-03-14 12:40               ` Mike Galbraith
2006-03-14 12:47                 ` Con Kolivas
2006-03-14 12:59                   ` Mike Galbraith [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=1142341195.11303.31.camel@homer \
    --to=efault@gmx.de \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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