From: Dipankar Sarma <dipankar@in.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Zwane Mwaikambo <zwane@linuxpower.ca>,
Andrew Morton <akpm@digeo.com>,
lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: 2.5.38-mm3
Date: Fri, 27 Sep 2002 22:44:24 +0530 [thread overview]
Message-ID: <20020927224424.A28529@in.ibm.com> (raw)
In-Reply-To: <502559422.1033113869@[10.10.2.3]>; from mbligh@aracnet.com on Fri, Sep 27, 2002 at 08:04:31AM -0700
On Fri, Sep 27, 2002 at 08:04:31AM -0700, Martin J. Bligh wrote:
> >> > What application were you all running ?
>
> Kernel compile on NUMA-Q looks like this:
>
> 125673 total
> 82183 default_idle
> 2288 d_lookup
> 1921 vm_enough_memory
> 1883 __generic_copy_from_user
> 1566 file_read_actor
> 1381 .text.lock.file_table <-------------
More likely, this is contention for the files_lock. Do you have any
lockmeter data ? That should give us more information. If so,
the files_struct_rcu isn't likely to help.
> 1168 find_get_page
> 1116 get_empty_filp
>
> Presumably that's the same thing? Interestingly, if I look back at
> previous results, I see it's about twice the cost in -mm as it is
> in mainline, not sure why ... at least against 2.5.37 virgin it was.
Not sure why it shows up more in -mm, but likely because -mm has
lot less contention on other locks like dcache_lock.
>
> > Please try running the files_struct_rcu patch where fget() is lockfree
> > and let me know what you see.
>
> Will do ... if you tell me where it is ;-)
Oh, the usual place -
http://sourceforge.net/project/showfiles.php?group_id=8875&release_id=112473
I wish sourceforge FRS continued to allow direct links to patches.
Thanks
--
Dipankar Sarma <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.
next prev parent reply other threads:[~2002-09-27 17:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 7:57 2.5.38-mm3 Andrew Morton
2002-09-26 12:24 ` 2.5.38-mm3 Dipankar Sarma
2002-09-26 12:29 ` 2.5.38-mm3 William Lee Irwin III
2002-09-26 12:40 ` 2.5.38-mm3 Dipankar Sarma
2002-09-26 12:42 ` 2.5.38-mm3 William Lee Irwin III
2002-09-26 13:05 ` 2.5.38-mm3 Dipankar Sarma
2002-09-26 13:17 ` 2.5.38-mm3 William Lee Irwin III
2002-09-26 13:29 ` 2.5.38-mm3 Zwane Mwaikambo
2002-09-26 13:39 ` 2.5.38-mm3 William Lee Irwin III
2002-09-26 13:46 ` 2.5.38-mm3 Zwane Mwaikambo
2002-09-27 8:27 ` 2.5.38-mm3 Dipankar Sarma
2002-09-27 9:20 ` 2.5.38-mm3 William Lee Irwin III
2002-09-27 9:58 ` 2.5.38-mm3 Dipankar Sarma
2002-09-27 15:04 ` 2.5.38-mm3 Martin J. Bligh
2002-09-27 17:14 ` Dipankar Sarma [this message]
2002-09-27 22:54 ` 2.5.38-mm3 William Lee Irwin III
2002-09-28 5:41 ` 2.5.38-mm3 Dipankar Sarma
2002-09-28 4:35 ` 2.5.38-mm3 Zwane Mwaikambo
2002-09-28 4:36 ` 2.5.38-mm3 William Lee Irwin III
2002-09-28 4:54 ` 2.5.38-mm3 Zwane Mwaikambo
2002-09-28 5:29 ` 2.5.38-mm3 Dipankar Sarma
2002-09-28 4:30 ` 2.5.38-mm3 Zwane Mwaikambo
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=20020927224424.A28529@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
--cc=wli@holomorphy.com \
--cc=zwane@linuxpower.ca \
/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;
as well as URLs for NNTP newsgroup(s).