From: Andi Kleen <andi@firstfloor.org>
To: Marek Szuba <scriptkiddie@wp.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Regular system 'hiccups' with 2.6.25+ on amd64 machines
Date: Thu, 02 Oct 2008 11:14:50 +0200 [thread overview]
Message-ID: <877i8rpddh.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20081001235106.57edede4@ifurita.akmm.lan> (Marek Szuba's message of "Wed, 1 Oct 2008 23:51:06 +0200")
Marek Szuba <scriptkiddie@wp.pl> writes:
>
> I would greatly appreciate it if you could look into the problem and
> let me know what is wrong - i.e. whether this is a bug, an
> unnecessarily-enabled feature, something that just needs a bit of
> tuning and so on. If you need any more information regarding the issue,
> my set-ups and so on, please don't hesitate to contact me (by
> writing to my e-mail address - I'm not subscribed to LKML at present)!
You could do a oprofile run (http://oprofile.sourceforge.net)
and see if it's something taking a lot of CPU time.
-Andi
--
ak@linux.intel.com
prev parent reply other threads:[~2008-10-02 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 21:51 Regular system 'hiccups' with 2.6.25+ on amd64 machines Marek Szuba
2008-10-01 22:09 ` Ray Lee
2008-10-02 20:22 ` Marek Szuba
2008-10-02 9:14 ` Andi Kleen [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=877i8rpddh.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scriptkiddie@wp.pl \
/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.