From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
To: Dave Hansen <dave@sr71.net>
Cc: Raghavendra KT <raghavendra.kt.linux@gmail.com>,
linux-kernel@vger.kernel.org, x86@kernel.org, linux-mm@kvack.org
Subject: Re: [RESEND][PATCH] mm: vmstats: tlb flush counters
Date: Sat, 20 Jul 2013 18:39:55 +0530 [thread overview]
Message-ID: <51EA8C23.5070408@linux.vnet.ibm.com> (raw)
In-Reply-To: <51E95932.5030902@sr71.net>
On 07/19/2013 08:50 PM, Dave Hansen wrote:
> On 07/19/2013 04:38 AM, Raghavendra KT wrote:
>> While measuring non - PLE performance, one of the bottleneck, I am seeing is
>> flush tlbs.
>> perf had helped in alaysing a bit there, but this patch would help
>> in precise calculation. It will aslo help in tuning the PLE window
>> experiments (larger PLE window
>> would affect remote flush TLBs)
>
> Interesting. What workload is that? I've been having problems finding
> workloads that are too consumed with TLB flushes.
>
Dave,
ebizzy is the one. and dbench to some small extent.
[root@codeblue ~]# cat /proc/vmstat |grep nr_tlb ;
/root/data/script/do_ebizzy.sh; cat /proc/vmstat |grep nr_tlb
nr_tlb_remote_flush 721
nr_tlb_remote_flush_received 923
nr_tlb_local_flush_all 13992
nr_tlb_local_flush_one 0
nr_tlb_local_flush_one_kernel 0
7482 records/s
real 120.00 s
user 86.69 s
sys 3746.57 s
nr_tlb_remote_flush 912896
nr_tlb_remote_flush_received 28261974
nr_tlb_local_flush_all 926272
nr_tlb_local_flush_one 0
nr_tlb_local_flush_one_kernel 0
next prev parent reply other threads:[~2013-07-20 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 23:44 [RESEND][PATCH] mm: vmstats: tlb flush counters Dave Hansen
2013-07-17 7:21 ` Ingo Molnar
2013-07-18 20:51 ` Andrew Morton
2013-07-19 8:28 ` Ingo Molnar
2013-07-19 15:51 ` Dave Hansen
2013-07-19 11:38 ` Raghavendra KT
2013-07-19 15:20 ` Dave Hansen
2013-07-20 13:09 ` Raghavendra K T [this message]
2013-07-22 10:06 ` Ingo Molnar
2013-07-22 16:59 ` Dave Hansen
2013-07-23 8:17 ` Ingo Molnar
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=51EA8C23.5070408@linux.vnet.ibm.com \
--to=raghavendra.kt@linux.vnet.ibm.com \
--cc=dave@sr71.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=raghavendra.kt.linux@gmail.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).