From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31101 invoked by alias); 25 Jan 2007 13:45:22 -0000 Received: (qmail 30894 invoked by uid 48); 25 Jan 2007 13:44:55 -0000 Date: Thu, 25 Jan 2007 13:45:00 -0000 Message-ID: <20070125134455.30892.qmail@sourceware.org> From: "fche at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20070111113517.3858.masami.hiramatsu.pt@hitachi.com> References: <20070111113517.3858.masami.hiramatsu.pt@hitachi.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug runtime/3858] Independent Runtime Module X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00199.txt.bz2 ------- Additional Comments From fche at redhat dot com 2007-01-25 13:44 ------- > I know I might merge the script sources. But sometimes (ex. running > systemtap on customer's servers), I can't do it and have to combine > the pre-compiled scripts. Could you explain why this merging needs to be done in kernel space? Why not in user-space after the fact? If the individual scripts emit timestamps, it would be straightforward. By merging in kernel space, we would probably be forcing all systemtap modules to synchronize while sharing a single set of buffers, slowing them all down. Can you describe a scenario where this is worth the cost? -- 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.