From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug testsuite/11373] let stap-client use cache
Date: Tue, 06 Jul 2010 16:00:00 -0000 [thread overview]
Message-ID: <20100706160018.6442.qmail@sourceware.org> (raw)
In-Reply-To: <20100312181334.11373.fche@redhat.com>
------- Additional Comments From fche at redhat dot com 2010-07-06 16:00 -------
While a stap-client can't validate & reuse a cached module, it
could still use the $SYSTEMTAP_DIR/cache to store .ko/.c files
returned from the server. The main benefit is that the cache
is automatically size-limited, and `pwd` is not littered with
.ko files.
--
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|systemtap at sources dot |brolley at redhat dot com
|redhat dot com |
Status|NEW |ASSIGNED
Summary|systemtap.server/server.exp |let stap-client use cache
|leaves stap_*.ko litter |
http://sourceware.org/bugzilla/show_bug.cgi?id=11373
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
prev parent reply other threads:[~2010-07-06 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 18:13 [Bug testsuite/11373] New: systemtap.server/server.exp leaves stap_*.ko litter fche at redhat dot com
2010-07-06 16:00 ` fche at redhat dot com [this message]
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=20100706160018.6442.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).