From: James Cloos <cloos@jhcloos.com>
To: linux-kernel@vger.kernel.org
Cc: Chris Mason <chris.mason@oracle.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org,
jfs-discussion@lists.sourceforge.net
Subject: Re: [Regression] Filesystem I/O is CPU-bound in rc7 and rc8
Date: Wed, 17 Feb 2010 15:04:47 -0500 [thread overview]
Message-ID: <m3d403632g.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <20100215154516.GB11057@think> (Chris Mason's message of "Mon, 15 Feb 2010 10:45:16 -0500")
While getting re-aquainted with perf, and after upgrading to the current
version, I see that do_page_fault, unmap_vmas, get_page_from_freelist,
handle_mm_fault, __do_fault and T.1339 tend to get the most time when the
kernel is spinning.
T.1339 is in this part of kallsyms:
,----< grep -E -C9 ^c1027750 /proc/kallsyms >
| c10266a0 T sched_setscheduler_nocheck
| c10266c0 T sched_setscheduler
| c10266e0 t do_sched_setscheduler
| c1026770 T sys_sched_setparam
| c1026790 T sys_sched_setscheduler
| c10267c0 T sched_fork
| c1026900 T task_oncpu_function_call
| c1026960 T print_cfs_rq
| c1027640 T scheduler_tick
| c1027750 t T.1339
| c10277f0 T schedule_tail
| c1027830 t ftrace_raw_output_sched_kthread_stop
| c1027930 t ftrace_raw_output_sched_kthread_stop_ret
| c1027a30 t ftrace_raw_output_sched_wait_task
| c1027b40 t ftrace_raw_output_sched_switch
| c1027c90 t ftrace_raw_output_sched_migrate_task
| c1027da0 t ftrace_raw_output_sched_process_wait
| c1027eb0 t ftrace_raw_output_sched_process_fork
| c1027fc0 t ftrace_raw_output_sched_stat_runtime
`----
suggesting that T.1339 is part of sched.
This leaves the impression that the issue is related to either
scheduling or paging.
I don't see any commits in the rc6..rc7 timeframe which stand out
as likely suspects.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2010-02-17 20:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 3:11 [Regression] Filesystem I/O is CPU-bound in rc7 and rc8 James Cloos
2010-02-14 16:40 ` James Cloos
2010-02-14 23:12 ` Rafael J. Wysocki
2010-02-15 15:45 ` Chris Mason
2010-02-15 19:27 ` James Cloos
2010-02-17 20:04 ` James Cloos [this message]
2010-02-19 21:02 ` Dave Airlie
2010-02-19 21:37 ` James Cloos
2010-02-19 22:03 ` Dave Airlie
2010-02-20 15:59 ` James Cloos
2010-02-21 2:12 ` James Cloos
2010-02-19 21:22 ` Mike Fedyk
2010-02-19 21:44 ` James Cloos
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=m3d403632g.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=chris.mason@oracle.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.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