From: Tim Chen <tim.c.chen@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrea Arcangeli <aarcange@redhat.com>,
Mel Gorman <mgorman@suse.de>, "Shi, Alex" <alex.shi@intel.com>,
Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michel Lespinasse <walken@google.com>,
Davidlohr Bueso <davidlohr.bueso@hp.com>,
"Wilcox, Matthew R" <matthew.r.wilcox@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Re: Performance regression from switching lock to rw-sem for anon-vma tree
Date: Tue, 25 Jun 2013 17:19:56 -0700 [thread overview]
Message-ID: <1372205996.22432.119.camel@schen9-DESK> (raw)
In-Reply-To: <1371660831.27102.663.camel@schen9-DESK>
On Wed, 2013-06-19 at 09:53 -0700, Tim Chen wrote:
> On Wed, 2013-06-19 at 15:16 +0200, Ingo Molnar wrote:
>
> > > vmstat for mutex implementation:
> > > procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu-----
> > > r b swpd free buff cache si so bi bo in cs us sy id wa st
> > > 38 0 0 130957920 47860 199956 0 0 0 56 236342 476975 14 72 14 0 0
> > > 41 0 0 130938560 47860 219900 0 0 0 0 236816 479676 14 72 14 0 0
> > >
> > > vmstat for rw-sem implementation (3.10-rc4)
> > > procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu-----
> > > r b swpd free buff cache si so bi bo in cs us sy id wa st
> > > 40 0 0 130933984 43232 202584 0 0 0 0 321817 690741 13 71 16 0 0
> > > 39 0 0 130913904 43232 224812 0 0 0 0 322193 692949 13 71 16 0 0
> >
> > It appears the main difference is that the rwsem variant context-switches
> > about 36% more than the mutex version, right?
> >
> > I'm wondering how that's possible - the lock is mostly write-locked,
> > correct? So the lock-stealing from Davidlohr Bueso and Michel Lespinasse
> > ought to have brought roughly the same lock-stealing behavior as mutexes
> > do, right?
> >
> > So the next analytical step would be to figure out why rwsem lock-stealing
> > is not behaving in an equivalent fashion on this workload. Do readers come
> > in frequently enough to disrupt write-lock-stealing perhaps?
Ingo,
I did some instrumentation on the write lock failure path. I found that
for the exim workload, there are no readers blocking for the rwsem when
write locking failed. The lock stealing is successful for 9.1% of the
time and the rest of the write lock failure caused the writer to go to
sleep. About 1.4% of the writers sleep more than once. Majority of the
writers sleep once.
It is weird that lock stealing is not successful more often.
Tim
> >
> > Context-switch call-graph profiling might shed some light on where the
> > extra context switches come from...
> >
> > Something like:
> >
> > perf record -g -e sched:sched_switch --filter 'prev_state != 0' -a sleep 1
> >
> > or a variant thereof might do the trick.
> >
>
> Ingo,
>
> It appears that we are having much more down write failure causing a process to
> block vs going to the slow path for the mutex case.
>
> Here's the profile data from
> perf record -g -e sched:sched_switch --filter 'prev_state != 0' -a sleep 1
>
> 3.10-rc4 (mutex implementation context switch profile)
>
> - 59.51% exim [kernel.kallsyms] [k] perf_trace_sched_switch
> - perf_trace_sched_switch
> - __schedule
> - 99.98% schedule
> + 33.07% schedule_timeout
> + 23.84% pipe_wait
> + 20.24% do_wait
> + 12.37% do_exit
> + 5.34% sigsuspend
> - 3.40% schedule_preempt_disabled
> __mutex_lock_common.clone.8
> __mutex_lock_slowpath
> - mutex_lock <---------low rate mutex blocking
> + 65.71% lock_anon_vma_root.clone.24
> + 19.03% anon_vma_lock.clone.21
> + 7.14% dup_mm
> + 5.36% unlink_file_vma
> + 1.71% ima_file_check
> + 0.64% generic_file_aio_write
> - 1.07% rwsem_down_write_failed
> call_rwsem_down_write_failed
> exit_shm
> do_exit
> do_group_exit
> SyS_exit_group
> system_call_fastpath
> - 27.61% smtpbm [kernel.kallsyms] [k] perf_trace_sched_switch
> - perf_trace_sched_switch
> - __schedule
> - schedule
> - schedule_timeout
> + 100.00% sk_wait_data
> + 0.46% swapper [kernel.kallsyms] [k] perf_trace_sched_switch
>
>
> ----------------------
> 3.10-rc4 implementation (rw-sem context switch profile)
>
> 81.91% exim [kernel.kallsyms] [k] perf_trace_sched_switch
> - perf_trace_sched_switch
> - __schedule
> - 99.99% schedule
> - 65.26% rwsem_down_write_failed <------High write lock blocking
> - call_rwsem_down_write_failed
> - 79.36% lock_anon_vma_root.clone.27
> + 52.64% unlink_anon_vmas
> + 47.36% anon_vma_clone
> + 12.16% anon_vma_fork
> + 8.00% anon_vma_free
> + 11.96% schedule_timeout
> + 7.66% do_exit
> + 7.61% do_wait
> + 5.49% pipe_wait
> + 1.82% sigsuspend
> 13.55% smtpbm [kernel.kallsyms] [k] perf_trace_sched_switch
> - perf_trace_sched_switch
> - __schedule
> - schedule
> - schedule_timeout
> 0.11% rcu_sched [kernel.kallsyms] [k] perf_trace_sched_switch
>
>
> Thanks.
>
> Tim
next prev parent reply other threads:[~2013-06-26 0:20 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 23:26 Performance regression from switching lock to rw-sem for anon-vma tree Tim Chen
2013-06-19 13:16 ` Ingo Molnar
2013-06-19 16:53 ` Tim Chen
2013-06-26 0:19 ` Tim Chen [this message]
2013-06-26 9:51 ` Ingo Molnar
2013-06-26 21:36 ` Tim Chen
2013-06-27 0:25 ` Tim Chen
2013-06-27 8:36 ` Ingo Molnar
2013-06-27 20:53 ` Tim Chen
2013-06-27 23:31 ` Tim Chen
2013-06-28 9:38 ` Ingo Molnar
2013-06-28 21:04 ` Tim Chen
2013-06-29 7:12 ` Ingo Molnar
2013-07-01 20:28 ` Tim Chen
2013-07-02 6:45 ` Ingo Molnar
2013-07-16 17:53 ` Tim Chen
2013-07-23 9:45 ` Ingo Molnar
2013-07-23 9:51 ` Peter Zijlstra
2013-07-23 9:53 ` Ingo Molnar
2013-07-30 0:13 ` Tim Chen
2013-07-30 19:24 ` Ingo Molnar
2013-08-05 22:08 ` Tim Chen
2013-07-30 19:59 ` Davidlohr Bueso
2013-07-30 20:34 ` Tim Chen
2013-07-30 21:45 ` Davidlohr Bueso
2013-08-06 23:55 ` Davidlohr Bueso
2013-08-07 0:56 ` Tim Chen
2013-08-12 18:52 ` Ingo Molnar
2013-08-12 20:10 ` Tim Chen
2013-06-28 9:20 ` Ingo Molnar
[not found] <1371165333.27102.568.camel@schen9-DESK>
[not found] ` <1371167015.1754.14.camel@buesod1.americas.hpqcorp.net>
2013-06-14 16:09 ` Tim Chen
2013-06-14 22:31 ` Davidlohr Bueso
2013-06-14 22:44 ` Tim Chen
2013-06-14 22:47 ` Michel Lespinasse
2013-06-17 22:27 ` Tim Chen
2013-06-16 9:50 ` Alex Shi
2013-06-17 16:22 ` Davidlohr Bueso
2013-06-17 18:45 ` Tim Chen
2013-06-17 19:05 ` Davidlohr Bueso
2013-06-17 22:28 ` Tim Chen
2013-06-17 23:18 ` Alex Shi
2013-06-17 23:20 ` Alex Shi
2013-06-17 23:35 ` Davidlohr Bueso
2013-06-18 0:08 ` Tim Chen
2013-06-19 23:11 ` Davidlohr Bueso
2013-06-19 23:24 ` Tim Chen
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=1372205996.22432.119.camel@schen9-DESK \
--to=tim.c.chen@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@intel.com \
--cc=andi@firstfloor.org \
--cc=dave.hansen@intel.com \
--cc=davidlohr.bueso@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.r.wilcox@intel.com \
--cc=mgorman@suse.de \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=riel@redhat.com \
--cc=walken@google.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;
as well as URLs for NNTP newsgroup(s).