Re: [PATCH v7 1/4] spinlock: A new lockref structure for lockless update of refcount

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 9/2/13 4:30 AM, Sedat Dilek wrote:
On Sun, Sep 1, 2013 at 5:55 PM, Linus Torvalds
<torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
On Sun, Sep 1, 2013 at 8:45 AM, Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote:

Samples: 160K of event 'cycles:pp', Event count (approx.): 77003901089
+  12,46%  t_lockref_from-  [kernel.kallsyms]     [k] irq_return
+   4,86%  t_lockref_from-  [kernel.kallsyms]     [k] lockref_get_or_lock
+   4,42%  t_lockref_from-  [kernel.kallsyms]     [k] __ticket_spin_lock
+   4,28%  t_lockref_from-  [kernel.kallsyms]     [k] __acct_update_integrals

You need to go into __ticket_spin_lock to see who the callers are.

Just go down to it and press enter to expand it (and then you need to
go and expand that entry too to get the callers)


I am new to perf usage.

One option for you is 'perf report --stdio ..'. That bypasses the tui.

David
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux