From: Selwyn Tang <selwyn@hectrix.com>
To: linux-mtd@lists.infradead.org
Subject: Re: high cpu usage using nftl for DOC2000
Date: Wed, 08 Oct 2003 17:46:21 +0800 [thread overview]
Message-ID: <3F83DCED.8090206@hectrix.com> (raw)
In-Reply-To: <1065171167.22491.53.camel@hades.cambridge.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2467 bytes --]
On 10/03/2003 04:52 PM, David Woodhouse wrote:
> Also, can you reset the profile counts (readprofile -r) and get a
> reading from the time when it's doing this alone, rather than including
> everything from boot onwards.
Here is the output of readprofile after reset and before nftld holds my cpu:
1 __generic_copy_to_user 0.0139
1 write_profile 0.0208
380 default_idle 9.5000
382 total 0.0003
Then I simply entered "ls /mnt/doc" (which is mounted at boot to
/dev/nftla1), and got the following result (I skipped those with one
occasion only):
2 __delay 0.0333
2 sock_poll 0.0500
2 unix_poll 0.0135
3 __const_udelay 0.0833
284 _DoC_WaitReady 2.8400
577 __rdtsc_delay 20.6071
1199 default_idle 29.9750
2084 total 0.0018
This is the output a few seconds later (also skipped some lines):
2 add_wait_queue 0.0500
2 __generic_copy_to_user 0.0278
2 sock_poll 0.0500
3 __delay 0.0500
3 unix_poll 0.0203
5 __const_udelay 0.1389
607 _DoC_WaitReady 6.0700
1199 default_idle 29.9750
1243 __rdtsc_delay 44.3929
3082 total 0.0026
So, __rdtsc_delay and _DoC_WaitReady seem to be the source of the
problem. I hope these will help you investigate. I have attached the
three outputs of readprofile for your reference.
> If it does it only sometimes, is there any pattern to when it starts or
> stops?
Once it has started, it would never stop. Sometimes, after fsck on the
doc, and remount, it becomes normal. But this time, I even tried booting
using the doc and perform some operations (like 'find .') and rebooting
back using my harddisk, and also tried booting using dos floppy and used
dinfo without the problem, but when back to Linux the problem was still
there.
I think dformating in dos is my last resort.
Selwyn
[-- Attachment #2: before --]
[-- Type: text/plain, Size: 230 bytes --]
1 __generic_copy_to_user 0.0139
1 write_profile 0.0208
380 default_idle 9.5000
382 total 0.0003
[-- Attachment #3: after --]
[-- Type: text/plain, Size: 1313 bytes --]
1 add_wait_queue 0.0250
1 do_softirq 0.0061
1 do_wp_page 0.0020
1 __find_get_page 0.0227
1 __generic_copy_to_user 0.0139
1 get_pid 0.0029
1 handle_IRQ_event 0.0109
1 journal_add_journal_head 0.0050
1 strncpy_from_user 0.0132
1 supplemental_group_member 0.0179
1 __switch_to 0.0054
1 sys_gettimeofday 0.0032
1 system_call 0.0179
1 tty_poll 0.0071
1 write_profile 0.0208
2 __delay 0.0333
2 sock_poll 0.0500
2 unix_poll 0.0135
3 __const_udelay 0.0833
284 _DoC_WaitReady 2.8400
577 __rdtsc_delay 20.6071
1199 default_idle 29.9750
2084 total 0.0018
[-- Attachment #4: after2 --]
[-- Type: text/plain, Size: 1484 bytes --]
1 do_anonymous_page 0.0047
1 do_softirq 0.0061
1 do_wp_page 0.0020
1 __find_get_page 0.0227
1 __generic_copy_from_user 0.0114
1 get_pid 0.0029
1 handle_IRQ_event 0.0109
1 journal_add_journal_head 0.0050
1 __loop_delay 0.0250
1 strncpy_from_user 0.0132
1 supplemental_group_member 0.0179
1 __switch_to 0.0054
1 sys_gettimeofday 0.0032
1 system_call 0.0179
1 tty_poll 0.0071
1 write_profile 0.0208
2 add_wait_queue 0.0500
2 __generic_copy_to_user 0.0278
2 sock_poll 0.0500
3 __delay 0.0500
3 unix_poll 0.0203
5 __const_udelay 0.1389
607 _DoC_WaitReady 6.0700
1199 default_idle 29.9750
1243 __rdtsc_delay 44.3929
3082 total 0.0026
next prev parent reply other threads:[~2003-10-08 9:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 6:54 high cpu usage using nftl for DOC2000 edward jose
2003-10-03 2:07 ` Selwyn Tang
2003-10-03 5:54 ` David Woodhouse
2003-10-03 8:22 ` Selwyn Tang
2003-10-03 8:52 ` David Woodhouse
2003-10-08 9:46 ` Selwyn Tang [this message]
2003-10-08 9:58 ` David Woodhouse
2003-10-08 10:16 ` Selwyn Tang
2003-10-08 10:22 ` David Woodhouse
2003-10-09 3:54 ` Selwyn Tang
2003-10-09 6:30 ` David Woodhouse
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=3F83DCED.8090206@hectrix.com \
--to=selwyn@hectrix.com \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox