From: Andrew Morton <akpm@digeo.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Dave Hansen <haveblue@us.ibm.com>,
William Lee Irwin III <wli@holomorphy.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Robert Love <rml@tech9.net>,
riel@surriel.com
Subject: Re: unusual scheduling performance
Date: Mon, 18 Nov 2002 10:52:36 -0800 [thread overview]
Message-ID: <3DD936F4.EDA4968A@digeo.com> (raw)
In-Reply-To: Pine.LNX.4.44.0211181031400.979-100000@blue1.dev.mcafeelabs.com
Davide Libenzi wrote:
>
> On Mon, 18 Nov 2002, Andrew Morton wrote:
>
> > Dave Hansen wrote:
> > >
> > > ...
> > > rwsem_down_write_failed: 133 133
> >
> > Possible culprit.
> >
> > Please stick a dump_stack() in rwsem_down_write_failed(), and add the below.
> > Suggest you stick with 2.5.47 to diagnose this. The loss of kksymoops
> > is a pain.
> >
> >
> > fs/eventpoll.c | 2 ++
> > 1 files changed, 2 insertions(+)
> >
> > --- 25/fs/eventpoll.c~hey Mon Nov 18 10:13:40 2002
> > +++ 25-akpm/fs/eventpoll.c Mon Nov 18 10:14:01 2002
> > @@ -328,6 +328,8 @@ void eventpoll_release(struct file *file
> > if (list_empty(lsthead))
> > return;
> >
> > + printk("hey!\n");
> > +
>
> Andrew, if you don't use epoll there's no way you get there.
Yup. That was a random stab based on recently-added down_write()
calls.
However the down_write isn't there in 2.5.47 so that's a false
lead. We'll need that dump_stack() output.
Here's Dave's profile. ep_notify_file_close() makes a small appearance.
The change you made to 2.5.48 will wipe that out. Neat.
0.058% 78 locks_remove_flock
0.062% 82 page_cache_readahead
0.062% 83 __generic_file_aio_read
0.065% 86 file_move
0.065% 87 dget_locked
0.066% 88 proc_pid_stat
0.067% 89 ep_notify_file_close
0.068% 91 get_pid_list
0.070% 93 update_atime
0.079% 105 get_unused_fd
0.085% 113 fget
0.090% 120 dput
0.091% 121 get_empty_filp
0.097% 129 system_call
0.100% 133 rwsem_down_write_failed
0.124% 164 vfs_follow_link
0.171% 227 file_read_actor
0.182% 241 __fput
0.221% 293 radix_tree_lookup
0.232% 307 atomic_dec_and_lock
0.250% 331 .text.lock.dec_and_lock
0.282% 374 try_to_wake_up
0.301% 398 kmap_atomic
0.309% 409 kunmap_atomic
0.326% 431 vfs_read
0.364% 482 .text.lock.namei
0.391% 518 __d_lookup
0.537% 710 link_path_walk
0.801% 1060 schedule
1.396% 1846 do_generic_mapping_read
25.275% 33416 poll_idle
66.319% 87678 __copy_to_user
100.000% 132206 total
next prev parent reply other threads:[~2002-11-18 18:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 8:18 unusual scheduling performance William Lee Irwin III
2002-11-18 16:34 ` Martin J. Bligh
2002-11-18 16:53 ` William Lee Irwin III
2002-11-18 17:53 ` Dave Hansen
2002-11-18 18:16 ` Andrew Morton
2002-11-18 18:34 ` Davide Libenzi
2002-11-18 18:52 ` Andrew Morton [this message]
2002-11-18 18:58 ` Davide Libenzi
2002-11-18 18:56 ` Dave Hansen
2002-11-18 18:59 ` Davide Libenzi
2002-11-18 20:17 ` William Lee Irwin III
2002-11-18 22:51 ` Dave Hansen
2002-11-18 23:09 ` Andrew Morton
2002-11-18 23:20 ` Davide Libenzi
2002-11-18 23:26 ` Dave Hansen
2002-11-18 23:30 ` Davide Libenzi
2002-11-18 23:33 ` Davide Libenzi
2002-11-20 14:12 ` Ingo Molnar
2002-11-20 22:19 ` William Lee Irwin III
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=3DD936F4.EDA4968A@digeo.com \
--to=akpm@digeo.com \
--cc=davidel@xmailserver.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=mingo@elte.hu \
--cc=riel@surriel.com \
--cc=rml@tech9.net \
--cc=wli@holomorphy.com \
/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