From: Brad Laue <brad@brad-x.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ksoftirqd using mysteriously high amounts of CPU time
Date: Thu, 11 Mar 2004 04:28:00 -0500 [thread overview]
Message-ID: <40503120.9000008@brad-x.com> (raw)
In-Reply-To: <4050271C.3070103@brad-x.com>
[-- Attachment #1: Type: text/plain, Size: 239 bytes --]
Brad Laue wrote:
> Hopefully the attached shows some irregularity. If not, I'll have to
> reply back in a few weeks when the problem recurs over the course of time.
And without further ado, the attachment. It's been a long day. :)
Brad
[-- Attachment #2: profile.txt --]
[-- Type: text/plain, Size: 2640 bytes --]
c0122bf0 current_kernel_time 2 0.0312
c0122d20 local_bh_enable 2 0.0139
c0137800 unlock_page 2 0.0208
c013ef10 __kmalloc 2 0.0156
c0155630 mark_buffer_dirty 2 0.0250
c0165760 poll_freewait 2 0.0250
c01df2b0 xfs_ichgtime 2 0.0075
c0202780 linvfs_get_block_core 2 0.0027
c0205310 linvfs_write 2 0.0069
c0216e90 fast_copy_page 2 0.0078
c0244b90 tty_write 2 0.0030
c0246020 tty_poll 2 0.0156
c0248670 n_tty_receive_buf 2 0.0005
c024b1e0 pty_unthrottle 2 0.0208
c024b240 pty_write 2 0.0043
c0109354 system_call 3 0.0682
c0152e70 vfs_write 3 0.0099
c0157cd0 alloc_buffer_head 3 0.0312
c01657b0 __pollwait 3 0.0144
c016e100 dnotify_parent 3 0.0156
c01b1e50 xfs_bmapi 3 0.0006
c024a3a0 normal_poll 3 0.0088
c0107090 cpu_idle 4 0.0625
c0153e60 fget 4 0.0625
c0165c60 sys_select 4 0.0032
c0216e30 fast_clear_page 4 0.0417
c0139280 generic_file_aio_write_nolock 5 0.0019
c0209d60 xfs_write 6 0.0028
c011ba10 __wake_up 7 0.0729
c0165960 do_select 8 0.0111
c0249920 read_chan 9 0.0042
c0156170 __block_prepare_write 12 0.0117
c02173c0 __copy_from_user_ll 12 0.0938
c010b570 handle_IRQ_event 13 0.1161
c0187210 write_profile 14 0.2188
c011b3c0 schedule 15 0.0107
c0217350 __copy_to_user_ll 47 0.4196
c0122c80 do_softirq 136 0.8500
c0107030 default_idle 9222 192.1250
00000000 total 9611 0.0063
next prev parent reply other threads:[~2004-03-11 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 21:16 ksoftirqd using mysteriously high amounts of CPU time Brad Laue
2004-03-10 23:57 ` Andrew Morton
2004-03-11 8:45 ` Brad Laue
2004-03-11 9:28 ` Brad Laue [this message]
2004-03-11 10:08 ` Andrew Morton
2004-03-11 14:05 ` Yury V. Umanets
2004-03-11 17:22 ` Brad Laue
2004-03-11 18:09 ` Yury V. Umanets
2004-03-11 18:21 ` Brad Laue
2004-03-11 18:24 ` Brad Laue
2004-03-12 17:51 ` Brad Laue
2004-03-11 14:00 ` Yury V. Umanets
[not found] <Pine.LNX.4.21.0403111916570.3466-100000@linux08.ece.utexas.edu>
2004-03-12 7:06 ` Brad Laue
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=40503120.9000008@brad-x.com \
--to=brad@brad-x.com \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox