From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Linux kernel <linux-kernel@vger.kernel.org>, linuxppc-dev@ozlabs.org
Subject: looking for help, attempting to debug high latency in 2.4 kernel
Date: Fri, 03 Dec 2004 15:58:36 -0600 [thread overview]
Message-ID: <41B0E18C.2060801@nortelnetworks.com> (raw)
Hi guys,
I'm running 2.4.22 on ppc32. Embedded system, just 74xx cpu, dual tulip network
links and fiberchannel card. Card has 1.5GB of memory, rootfs is tmpfs, system
has some NFS mounts.
We're seeing userspace delayed for almost a second every so often. No idea
what's causing it.
We've got scheduler instrumentation showing a usespace task starting to run,
then a bunch of tasks being put on the runqueue, and finally we wake up and
start running normally again almost a full second later. The timing is not
exactly the same in each case, but it's usually close to a second of delay.
I'm looking for some tips on how to go about tracking this down.
Where are my delays likely to be coming from? Long-running code paths? Long
periods with interrupts off? I dunno where to start.
Would porting lockmeter be a good idea? Is there anyone who's already done this
for ppc?
I appreciate any help.
Thanks,
Chris
reply other threads:[~2004-12-03 22:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41B0E18C.2060801@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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.