public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Martin Hunt <hunt@redhat.com>
To: sourceware-bugzilla@sourceware.org
Cc: systemtap@sources.redhat.com
Subject: Re: [Bug translator/2293] confirm preemption/interrupt blocking in 	systemtap probes
Date: Wed, 29 Mar 2006 18:05:00 -0000	[thread overview]
Message-ID: <1143655519.2636.10.camel@dragon> (raw)
In-Reply-To: <20060329115458.29001.qmail@sourceware.org>

On Wed, 2006-03-29 at 11:54 +0000, fche at redhat dot com wrote:

> I recommend opening a new bug against the runtime, addressing specifically the
> issue of I/O buffering near the time of shutdown.  I recall suggesting looking
> into whether stpd and the kernel-side runtime message handler can work together
> to drain the buffers before starting the module_exit process, to provide the
> maximum static space to the end probes.  (That space amount would
> uncoincidentally match the command line option "-s NUM" to the initial
> compilation stage, and thus make some intuitive sense to the user.)  Did you try
> that?

I think I originally suggested it, and I have thought further about it.
I hoped to find a better solution than imposing another limit users have
to compute. For collecting large amounts of data, MAXMAPENTRIES needs
raised and then you have to calculate how much space that data will take
up when "printed" into the output buffers.  Another problem is that for
relayfs the buffer is divided into per-cpu sub-buffers. So the maximum
data that can be sent is NUM/cpus. 

Martin

  reply	other threads:[~2006-03-29 18:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 17:14 [Bug translator/2293] New: " fche at redhat dot com
2006-02-22 15:06 ` [Bug translator/2293] " fche at redhat dot com
2006-02-22 20:07 ` hunt at redhat dot com
2006-02-23 20:42 ` fche at redhat dot com
2006-02-27 17:32 ` hunt at redhat dot com
2006-02-27 18:56   ` disabled interrupts (Was bug #2293 Frank Ch. Eigler
2006-02-27 19:16     ` Martin Hunt
2006-02-27 20:01       ` Frank Ch. Eigler
2006-02-27 21:10         ` Martin Hunt
2006-03-29  7:06 ` [Bug translator/2293] confirm preemption/interrupt blocking in systemtap probes hunt at redhat dot com
2006-03-29 11:55 ` fche at redhat dot com
2006-03-29 18:05   ` Martin Hunt [this message]
2006-03-29 20:18     ` Frank Ch. Eigler
2006-05-05 16:09     ` Vara Prasad
2006-03-29 18:05 ` hunt at redhat dot com
2006-05-01 14:20 ` fche at redhat dot com
2006-05-05 16:10 ` prasadav at us dot ibm dot com
     [not found] ` <20060505160951.1801.qmail@sourceware.org>
2006-05-05 16:38   ` Frank Ch. Eigler

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=1143655519.2636.10.camel@dragon \
    --to=hunt@redhat.com \
    --cc=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).