From: Ingo Molnar <mingo@elte.hu>
To: Gregory Haskins <ghaskins@novell.com>
Cc: Mike Galbraith <efault@gmx.de>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [revert] mysql+oltp regression
Date: Mon, 11 Aug 2008 15:14:00 +0200 [thread overview]
Message-ID: <20080811131400.GA909@elte.hu> (raw)
In-Reply-To: <48A038A6.4010104@novell.com>
* Gregory Haskins <ghaskins@novell.com> wrote:
>>> Speaking of this: Another patch I submitted to you Ingo (had to do
>>> with updating the load_weight inside task_setprio) seems to also
>>> have this phenomenon: e.g. its technically correct but further
>>> testing has revealed negative repercussions elsewhere. So please
>>> ignore that patch (or revert if you already pulled in, but I don't
>>> think you have). Ill try to look into this issue as well.
>>
>> ok, under which thread/subject is that? Not queued in tip/sched/*
>> yet, correct?
>>
> Here is the original thread:
>
> http://lkml.org/lkml/2008/7/3/416
>
> I do not believe you have queued it anywhere (public anyway) yet.
>
> Note I have already invalidated 1/2, and now I am retracting 2/2 as
> well. (1/2 is actually a bogus patch, 2/2 is "technically correct"
> but causes ripples in the load balancer that need to be sorted out
> first.
ok, thanks. I'm curious, what are those ripple effects? Stability or
performance?
Ingo
next prev parent reply other threads:[~2008-08-11 13:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 11:32 [revert] mysql+oltp regression Mike Galbraith
2008-08-11 11:43 ` Ingo Molnar
2008-08-11 12:27 ` Gregory Haskins
2008-08-11 12:48 ` Ingo Molnar
2008-08-11 12:51 ` Ingo Molnar
2008-08-11 13:03 ` Gregory Haskins
2008-08-11 13:14 ` Ingo Molnar [this message]
2008-08-11 13:19 ` Gregory Haskins
2008-08-11 13:27 ` Gregory Haskins
2008-08-11 13:31 ` Ingo Molnar
2008-08-11 13:29 ` 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=20080811131400.GA909@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=ghaskins@novell.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.