From: "anil dot s dot keshavamurthy at intel dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/2062] Return probes does not scale well on SMP box
Date: Tue, 18 Apr 2006 20:38:00 -0000 [thread overview]
Message-ID: <20060418203816.31343.qmail@sourceware.org> (raw)
In-Reply-To: <20051216010933.2062.anil.s.keshavamurthy@intel.com>
------- Additional Comments From anil dot s dot keshavamurthy at intel dot com 2006-04-18 20:38 -------
> why not just store data per cpu/core
Storing it in per cpu might not work here as in some cases the function enter
might be called on one cpu and the by the time that function returns it could
have migrated to a different cpu's and hence return is executed from different
cpu. So we have to do global search for the return probe instance related to
that perticular task and hence per cpu/core is not feasible.
However if we store the return probe instances in the task structure itself(by
extending the task struct)then we can completly eliminate the locks for return
probes and return probes can be made to run in parallel. We have to convince
the linux community for extension of task struct.
-Anil
--
http://sourceware.org/bugzilla/show_bug.cgi?id=2062
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2006-04-18 20:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 1:58 [Bug kprobes/2062] New: " anil dot s dot keshavamurthy at intel dot com
2006-04-18 5:35 ` [Bug kprobes/2062] " guanglei at cn dot ibm dot com
2006-04-18 5:37 ` guanglei at cn dot ibm dot com
2006-04-18 18:09 ` jkenisto at us dot ibm dot com
2006-04-18 19:32 ` James Dickens
2006-04-18 19:32 ` jamesd dot wi at gmail dot com
2006-04-18 20:22 ` jkenisto at us dot ibm dot com
2006-04-18 20:38 ` anil dot s dot keshavamurthy at intel dot com [this message]
2006-04-18 22:04 ` jkenisto at us dot ibm dot com
2006-04-18 23:48 ` anil dot s dot keshavamurthy at intel dot com
2006-04-19 3:54 ` James Dickens
[not found] ` <20060418234829.24893.qmail@sourceware.org>
2006-04-18 23:54 ` Frank Ch. Eigler
2006-04-19 1:02 ` guanglei at cn dot ibm dot com
2006-04-19 1:07 ` guanglei at cn dot ibm dot com
2006-04-19 3:55 ` jamesd dot wi at gmail dot com
2006-04-19 21:44 ` jkenisto at us dot ibm dot com
2006-04-19 21:56 ` fche at redhat dot com
2006-04-19 23:53 ` jkenisto at us dot ibm dot com
2006-04-20 0:22 ` jkenisto at us dot ibm dot com
2006-07-07 9:24 ` guanglei at cn dot ibm dot com
2006-07-07 9:27 ` guanglei at cn dot ibm dot com
2006-07-07 17:47 ` jkenisto at us dot ibm dot com
2006-07-07 23:32 ` jkenisto at us dot ibm dot com
2006-07-07 23:34 ` jkenisto at us dot ibm dot com
2006-07-07 23:55 ` jkenisto at us dot ibm dot com
2006-07-08 5:14 ` guanglei at cn dot ibm dot com
2006-07-11 10:45 ` bibo dot mao at intel dot com
2006-07-11 11:15 ` ananth at in dot ibm dot com
2006-07-12 4:35 ` bibo dot mao at intel dot com
2006-07-13 6:10 ` bibo dot mao at intel dot com
2006-07-13 6:12 ` bibo dot mao at intel dot com
2006-07-13 6:21 ` bibo dot mao at intel dot com
2006-07-13 19:44 ` jkenisto at us dot ibm dot com
2006-07-14 8:13 ` bibo dot mao at intel dot com
2006-11-16 1:15 ` jkenisto at us dot ibm dot com
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=20060418203816.31343.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).