From: Jayson King <dev@jaysonking.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, torvalds@linux-foundation.org,
a.p.zijlstra@chello.nl, shaggy@linux.vnet.ibm.com, rjw@sisk.pl,
fabio.comolli@gmail.com
Subject: Re: Disregard: was Re: large intermittent latency spike 2.6.28 (and 2.6.27.10), bisect commit ca7e716c7833aeaeb8fedd6d004c5f5d5e14d325 -> Revert "sched_clock: prevent scd->clock from moving backwards"
Date: Wed, 31 Dec 2008 04:41:18 -0600 [thread overview]
Message-ID: <495B4C4E.8040202@jaysonking.com> (raw)
In-Reply-To: <495B40C1.4080305@jaysonking.com>
> Please disregard this. I just had a latency spike again, so this is
> not the change I'm looking for... I'll need to look for what is
> causing it again, apparently not only the make -j 3 I thought, and do
> another test.
No I was just running the old vanilla kernel again by mistake... So
disregard the disregard, the problem still stands :) (now is probably a
good time to get some sleep... sorry for spamming)
I should tell grub to change the default kernel when updating, so stupid
things like this won't happen.
Jayson
next prev parent reply other threads:[~2008-12-31 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 21:47 large intermittent latency spike 2.6.28 (and 2.6.27.10), bisect commit ca7e716c7833aeaeb8fedd6d004c5f5d5e14d325 -> Revert "sched_clock: prevent scd->clock from moving backwards" Jayson King
2008-12-31 8:54 ` [PATCH] sched_clock: prevent scd->clock from moving backwards, take #2 Ingo Molnar
2008-12-31 18:49 ` Jayson King
2008-12-31 9:52 ` Disregard: was Re: large intermittent latency spike 2.6.28 (and 2.6.27.10), bisect commit ca7e716c7833aeaeb8fedd6d004c5f5d5e14d325 -> Revert "sched_clock: prevent scd->clock from moving backwards" Jayson King
2008-12-31 10:41 ` Jayson King [this message]
2008-12-31 11:00 ` Arjan van de Ven
2008-12-31 22:27 ` Jayson King
2008-12-31 22:38 ` Fabio Comolli
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=495B4C4E.8040202@jaysonking.com \
--to=dev@jaysonking.com \
--cc=a.p.zijlstra@chello.nl \
--cc=fabio.comolli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=shaggy@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.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.