From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Tom Zanussi <zanussi@us.ibm.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
James Dickens <jamesd.wi@gmail.com>,
systemtap@sources.redhat.com
Subject: Re: MAXACTION exceeded error while using systemtap
Date: Wed, 28 Dec 2005 20:38:00 -0000 [thread overview]
Message-ID: <20051228201249.GA8405@dmt.cnet> (raw)
In-Reply-To: <17330.60599.330907.78327@tut.ibm.com>
> > I think that SystemTap needs some method to periodically (or when memory
> > pressure arrives) dump the parts of the array to userspace via
> > relayfs.
>
> See my previous reply for one way you could do this i.e. the
> kmalloc-stacks example.
Will take a look - seems promising.
> > relayfs already supports such mechanism with its "sub-buffer" structure,
> > where the userspace reader is allowed to read full buffers (thus freeing
> > them afterwards) while the hooks continue to push data to empty or
> > partially filled buffers.
> >
> > James mentions that
> >
> > "btw MAXACTION really can't work reliably what happens when the box is
> > underload, say with 4 gigabit nics all being flooded with data, and
> > you are probing a function in the fast path?
> >
> > Not everyone has a box that can sum 4 billion numbers in less than a minute."
> >
> > relayfs works in two modes once its memory pool is full:
> >
> > - panic's
> > - drops new entries
> >
> > I imagine that by using relayfs to send data to userspace one should
> > automatically get those very important features.
>
> I'm not sure what you mean - relayfs can be used in either 'overwrite'
> or 'no-overwrite' modes; if its memory pool is full, 'overwrite' mode
> overwrites the oldest entries, while 'no-overwrite' mode drops new
> entries - there should be no 'panic's' anywhere in there. ;-)
Indeed - there's no "panic" anywhere. Your description is accurate (unlike
mine's) :)
next prev parent reply other threads:[~2005-12-28 20:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 21:56 Stone, Joshua I
2005-12-06 22:11 ` Frank Ch. Eigler
2005-12-07 20:53 ` Martin Hunt
2005-12-07 21:09 ` Frank Ch. Eigler
2005-12-07 22:29 ` Martin Hunt
2005-12-07 23:07 ` Frank Ch. Eigler
2005-12-08 8:55 ` Martin Hunt
2005-12-08 12:52 ` James Dickens
2005-12-08 13:57 ` Frank Ch. Eigler
2005-12-28 19:06 ` Marcelo Tosatti
2005-12-28 20:12 ` Tom Zanussi
2005-12-28 20:38 ` Marcelo Tosatti [this message]
2005-12-28 21:13 ` Frank Ch. Eigler
2005-12-08 13:37 ` Frank Ch. Eigler
-- strict thread matches above, loose matches on Subject: below --
2005-12-08 17:50 Stone, Joshua I
2005-12-06 20:41 Stone, Joshua I
2005-12-06 20:55 ` Frank Ch. Eigler
2005-12-06 16:40 Badari Pulavarty
2005-12-06 16:59 ` Frank Ch. Eigler
2005-12-07 1:10 ` Badari Pulavarty
2005-12-07 15:21 ` William Cohen
2005-12-07 16:37 ` Badari Pulavarty
2005-12-06 17:01 ` Hien Nguyen
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=20051228201249.GA8405@dmt.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=fche@redhat.com \
--cc=jamesd.wi@gmail.com \
--cc=systemtap@sources.redhat.com \
--cc=zanussi@us.ibm.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).