All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	RT <linux-rt-users@vger.kernel.org>
Subject: Re: [RFC][PATCH 0/3] update to cpupri algorithm
Date: Sat, 30 Jul 2011 10:16:36 +0200	[thread overview]
Message-ID: <1312013796.8752.63.camel@marge.simson.net> (raw)
In-Reply-To: <1312009931.8752.53.camel@marge.simson.net>

On Sat, 2011-07-30 at 09:12 +0200, Mike Galbraith wrote:
> y profile looks much better, but jitter proggy using posix-timers on 56
> cores warms up a spot you know all about.  Lucky me, I know where fixes
> for that bugger live.

JiitterChasing::TheEnd() doesn't exist does it?  Aw poo.

30999      0.05%  [k] lock_timer
31000             |
31001             --- do_schedule_next_timer
31002                 dequeue_signal
31003                |
31004                |--87.94%-- sys_rt_sigtimedwait
31005                |          system_call_fastpath
31006                |          |
31007                |          |--20.24%-- 0x7f0935011f27
31008                |          |          do_sigwait

# dso: [kernel.kallsyms]
# Events: 118K cycles
#
# Overhead                               Symbol
# ........  ...................................
#
    22.82%  [k] _raw_spin_lock_irqsave
            |          
            |--32.46%-- rt_mutex_trylock
            |          tty_write_lock
            |          tty_write
            |          vfs_write
            |          sys_write
            |          system_call_fastpath
            |          |          
            |          |--4.38%-- 0x7f46672a30f0
            |          |          __GI___libc_write
...
            |          
            |--32.20%-- rt_mutex_slowlock
            |          tty_write_lock
            |          tty_write
            |          vfs_write
            |          sys_write
            |          system_call_fastpath
            |          |          
            |          |--4.71%-- 0x7f46672a30f0
            |          |          __GI___libc_write
...
            |--25.36%-- rcu_sched_qs
            |          __schedule
            |          |          
            |          |--52.52%-- preempt_schedule
            |          |          try_to_wake_up
            |          |          signal_wake_up
            |          |          send_sigqueue
            |          |          posix_timer_event
            |          |          posix_timer_fn
            |          |          run_hrtimer_softirq
            |          |          run_ksoftirqd
            |          |          kthread
            |          |          kernel_thread_helper
            |          |          
            |           --47.48%-- schedule
            |                     rt_spin_lock_slowlock
            |                     lock_timer
            |                     do_schedule_next_timer
            |                     dequeue_signal
            |                     |          
            |                     |--63.61%-- sys_rt_sigtimedwait
            |                     |          system_call_fastpath
            |                     |          |          
            |                     |          |--9.26%-- 0x7f3c840acf27
            |                     |          |          do_sigwait
...
            |                     |          |          do_sigwait
            |                     |           --5.58%-- [...]
            |                     |          
            |                      --36.39%-- get_signal_to_deliver
            |                                do_signal
            |                                do_notify_resume
            |                                int_signal
            |                                |          
            |                                |--6.17%-- 0x7f1dd90610f0
            |                                |          __GI___libc_write
...
            |          
            |--6.54%-- rt_mutex_slowunlock
            |          tty_write_unlock
            |          tty_write
            |          vfs_write
            |          sys_write
            |          system_call_fastpath
            |          |          
            |          |--6.06%-- 0x7f11267610f0
            |          |          __GI___libc_write




  reply	other threads:[~2011-07-30  8:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29 15:13 [RFC][PATCH 0/3] update to cpupri algorithm Steven Rostedt
2011-07-29 15:13 ` [RFC][PATCH 1/3] cpupri: Add profiling Steven Rostedt
2011-07-29 15:13 ` [RFC][PATCH 2/3] cpupri: Remove vector locks and read entire loop Steven Rostedt
2011-07-29 15:13 ` [RFC][PATCH 3/3] cpupri: Add atomic vector count to speed up loop Steven Rostedt
2011-07-29 15:38 ` [RFC][PATCH 0/3] update to cpupri algorithm Mike Galbraith
2011-07-29 18:24 ` Mike Galbraith
2011-07-30  7:12   ` Mike Galbraith
2011-07-30  8:16     ` Mike Galbraith [this message]
2011-07-30  9:19 ` Mike Galbraith
2011-08-01 14:18   ` Steven Rostedt
2011-08-01 18:41     ` Mike Galbraith
2011-08-01 18:54       ` Steven Rostedt
2011-08-01 19:06         ` Mike Galbraith
2011-08-02  8:59         ` Mike Galbraith
2011-08-02  8:46     ` Mike Galbraith

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=1312013796.8752.63.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.