public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/3858] Independent Runtime Module
Date: Thu, 15 Feb 2007 15:26:00 -0000	[thread overview]
Message-ID: <20070215152641.16987.qmail@sourceware.org> (raw)
In-Reply-To: <20070111113517.3858.masami.hiramatsu.pt@hitachi.com>


------- Additional Comments From fche at redhat dot com  2007-02-15 15:26 -------
(In reply to comment #8)
> In many cases, IMHO, the gcc/kernel-debuginfo is not installed on the customer's
> servers because of security and diskspace. So, we can't compile the scripts
> on those servers.

This situation is already addressed to some extent with our cross-compilation
capabilities.  (See the relevant war story wiki page for an example.)

> I'd like to share only buffers, not variables.
> I think the sharing buffer interfaces will not increase contention
> slowdown. What would you think about this?

Unless I am mistaken, sharing buffers by nature increases contention.
Concurrently executing probes would have to use some mutual exclusion
to write into the same buffer.  Plus they would probably have to include
some additional information with every record to identify the script
that produced it.

> I think we might as well focus on the "I/O buffer sharing by pre-compiled
> modules" issue. The title of this bug is very confusion, so I suggest that 
> we should make a new entry to discuss this issue.

Perhaps we can lump it in with the flight recorder functionality.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=3858

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2007-02-15 15:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-11 11:35 [Bug runtime/3858] New: " masami dot hiramatsu dot pt at hitachi dot com
2007-01-21 23:49 ` [Bug runtime/3858] " fche at redhat dot com
2007-01-22  4:24 ` masami dot hiramatsu dot pt at hitachi dot com
2007-01-22 19:20 ` fche at redhat dot com
2007-01-25 12:37 ` masami dot hiramatsu dot pt at hitachi dot com
2007-01-25 13:45 ` fche at redhat dot com
2007-01-26 13:54 ` masami dot hiramatsu dot pt at hitachi dot com
2007-01-28 15:07 ` fche at redhat dot com
2007-01-29 11:35 ` masami dot hiramatsu dot pt at hitachi dot com
2007-02-15 15:26 ` fche at redhat dot com [this message]
2007-02-16 13:06 ` hiramatu at sdl dot hitachi dot co dot jp
2007-02-16 13:09 ` hiramatu at sdl dot hitachi dot co dot jp
2007-02-16 15:54 ` hunt at redhat dot com
2007-05-17  5:57 ` hiramatu at sdl dot hitachi dot co dot jp
2007-05-17  6:41 ` masami dot hiramatsu dot pt at hitachi dot com
2007-08-07 19:51 ` mhiramat at redhat dot com
2007-08-17 22:04 ` [Bug runtime/3858] option to share trace buffers between probe modules fche at redhat dot com
2007-10-17 21:45 ` mhiramat at redhat dot com
2007-10-17 21:54 ` mhiramat at redhat dot com
2007-10-17 23:02 ` fche at redhat dot com
2007-10-18 14:06 ` hunt at redhat dot com
2007-10-18 14:58 ` mhiramat at redhat dot com
2007-10-18 18:13 ` fche at redhat dot com
2007-10-22 19:49 ` mhiramat at redhat dot com
2007-10-24 22:04 ` mhiramat at redhat dot com
2007-10-30 19:48 ` mhiramat at redhat dot com
2007-11-09 18:47 ` mhiramat at redhat 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=20070215152641.16987.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).