From: Andrew Morton <akpm@digeo.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu, rml@tech9.net,
riel@surriel.com, akpm@zip.com.au
Subject: Re: unusual scheduling performance
Date: Mon, 18 Nov 2002 10:16:50 -0800 [thread overview]
Message-ID: <3DD92E92.EEB9ECD6@digeo.com> (raw)
In-Reply-To: 3DD92914.1060301@us.ibm.com
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");
+
/*
* We don't want to get "file->f_ep_lock" because it is not
* necessary. It is not necessary because we're in the "struct file"
_
next prev parent reply other threads:[~2002-11-18 18:10 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 [this message]
2002-11-18 18:34 ` Davide Libenzi
2002-11-18 18:52 ` Andrew Morton
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=3DD92E92.EEB9ECD6@digeo.com \
--to=akpm@digeo.com \
--cc=akpm@zip.com.au \
--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