public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Mike Galbraith <efault@gmx.de>
Cc: lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@osdl.org>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	Peter Williams <pwil3058@bigpond.net.au>
Subject: Re: [2.6.16-mm1 patch] throttling tree patches
Date: Sat, 25 Mar 2006 00:52:39 +1100	[thread overview]
Message-ID: <200603250052.40235.kernel@kolivas.org> (raw)
In-Reply-To: <1143205342.7741.104.camel@homer>

On Saturday 25 March 2006 00:02, Mike Galbraith wrote:
> On Fri, 2006-03-24 at 23:34 +1100, Con Kolivas wrote:
> > I feel this discussion may degenerate beyond this point. Should we say to
> > agree to disagree at this point? I don't like these changes.
>
> Why should it degenerate?  You express your concerns, I answer them.
> You don't have to agree with me, and I don't have to agree with you.
> That's no reason for the discussion to degenerate.

By degenerate I mean get stuck in an endless loop. I don't have the energy for 
cyclical discussions where no conclusive endpoint can ever be reached. That 
is the nature of what we're discussing. Everything is some sort of compromise 
and you're moving one set of compromises for another which means this can be 
debated forever without a right or wrong.

The merits of throttling seem obvious with a sliding scale between 
interactivity and fairness. These other changes, to me, do not. On the 
interactivity side I only have interbench for hard data, and it is showing me 
regressions consistent with my concerns from these other "cleanups". You'll 
trade some other advantage for these and we'll repeat the discussion all over 
again. Rinse and repeat.

Cheers,
Con

  reply	other threads:[~2006-03-24 13:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-24 11:03 [2.6.16-mm1 patch] throttling tree patches Mike Galbraith
2006-03-24 11:07 ` Mike Galbraith
2006-03-24 11:16   ` Mike Galbraith
2006-03-24 11:21     ` Mike Galbraith
2006-03-24 11:24       ` Mike Galbraith
2006-03-24 11:28         ` Mike Galbraith
2006-03-24 11:56           ` Con Kolivas
2006-03-24 11:55         ` Con Kolivas
2006-03-24 11:54       ` Con Kolivas
2006-03-24 11:56     ` Con Kolivas
2006-03-24 12:21       ` Mike Galbraith
2006-03-24 12:34         ` Con Kolivas
2006-03-24 13:02           ` Mike Galbraith
2006-03-24 13:52             ` Con Kolivas [this message]
2006-03-24 14:10               ` Mike Galbraith
2006-03-24 11:38   ` Con Kolivas
2006-03-24 11:37 ` Con Kolivas
2006-03-25  0:25   ` Peter Williams
2006-03-25  5:06     ` Mike Galbraith
2006-03-25  6:18       ` [2.6.16-mm1 patch] ignore timewarps Mike Galbraith
2006-03-25  0:37 ` [2.6.16-mm1 patch] throttling tree patches Peter Williams
2006-03-25  5:11   ` Mike Galbraith

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=200603250052.40235.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=akpm@osdl.org \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.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