From: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
To: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Cc: balbir@linux.vnet.ibm.com, Peter Zijlstra <peterz@infradead.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Alexis Bruemmer <alexisb@us.ibm.com>,
Balbir Singh <balbir@in.ibm.com>,
Badari Pulavarty <pbadari@us.ibm.com>,
Max Asbock <amax@us.ibm.com>, linux-mm <linux-mm@kvack.org>,
Bharata B Rao <bharata@in.ibm.com>
Subject: Re: VMA lookup with RCU
Date: Mon, 22 Oct 2007 15:24:10 +0530 [thread overview]
Message-ID: <471C7342.3010004@linux.vnet.ibm.com> (raw)
In-Reply-To: <470A6010.6000108@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
[snip]
>
> All the above test results has the impact of oprofile included. Running
> oprofile also may significantly increase mmap_sem contention.
>
> I Will run the tests again without oprofile to understand the impact of
> oprofile itself.
>
Hi,
I have run the same tests without oprofile and also tried to plot the
impact of oprofile.
There are two attached graphs.
rcu-vma-scaling.png contains the plot of Peter's RCU-VMA lookup without
running oprofile.
There are some variations beyond 10 CPUs. I am trying to wonder if those
were due to errors in test/measurement!
oprofile-scaling.png plots similar tests with and without oprofile enabled.
We can see more impact beyond 12 CPUs.
--Vaidy
[-- Attachment #2: oprofile-scaling.png --]
[-- Type: image/png, Size: 4028 bytes --]
[-- Attachment #3: rcu-vma-scaling.png --]
[-- Type: image/png, Size: 4808 bytes --]
next prev parent reply other threads:[~2007-10-22 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46F01289.7040106@linux.vnet.ibm.com>
[not found] ` <20070918205419.60d24da7@lappy>
[not found] ` <1191436672.7103.38.camel@alexis>
2007-10-03 19:40 ` VMA lookup with RCU Peter Zijlstra
2007-10-03 19:54 ` Peter Zijlstra
2007-10-04 15:42 ` Vaidyanathan Srinivasan
2007-10-04 17:21 ` Peter Zijlstra
2007-10-07 7:47 ` Nick Piggin
2007-10-08 7:51 ` Peter Zijlstra
2007-10-08 9:32 ` Balbir Singh
2007-10-08 16:51 ` Vaidyanathan Srinivasan
2007-10-08 8:17 ` Nick Piggin
2007-10-22 9:54 ` Vaidyanathan Srinivasan [this message]
2007-10-08 17:02 ` Vaidyanathan Srinivasan
2007-10-08 17:11 ` Vaidyanathan Srinivasan
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=471C7342.3010004@linux.vnet.ibm.com \
--to=svaidy@linux.vnet.ibm.com \
--cc=alexisb@us.ibm.com \
--cc=amax@us.ibm.com \
--cc=balbir@in.ibm.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=bharata@in.ibm.com \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=pbadari@us.ibm.com \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).