public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: David Smith <dsmith@redhat.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: systemtap@sources.redhat.com
Subject: Re: precompiled probing scenarios
Date: Mon, 23 Oct 2006 20:36:00 -0000	[thread overview]
Message-ID: <453D27A8.3050407@redhat.com> (raw)
In-Reply-To: <20061020201318.GD17981@elastic.org>

Frank Ch. Eigler wrote:
> Hi -
> 
> dsmith wrote:
>> [...]
>> I don't hash the getuid(), since:
>> - by default your cache is stored in your home directory
>> - who you are doesn't change the pass 2-4 output
> 
> That's all true.  One possible reason for including getuid() anyway is
> so that two different sudo-empowered people can run the same script at
> the same time without one having to disable his cache.

Ah - makes sense, I've added this.

>> Nope.  I actually cache the module and the C file so I can skip pass 3 
>> but still preserve semantics.
> 
> OK.
> 
>> Hmm.  How about something like:
>>   Pass 3: Using cached 
>> /home/dsmith/.stap_cache/d/8/stap_d833fd040735ddde57a23bebb4456542_201.c
>>   Pass 4: Using cached 
>> /home/dsmith/.stap_cache/d/8/stap_d833fd040735ddde57a23bebb4456542_201.ko
> 
> Works for me.

OK, I've implemented this.

> (It may be a worthwhile minor simplification to use
> one-byte /d8/ as a partitioning subdirectory rather than two-nibble
> /d/8/ scheme.  256 files in a single directory are well handled in our
> filesystems.)

I did it this way because ccache did it this way.  My sense is that it 
was done this way to make sure the directories with cached files didn't 
end up too large (not the partition directories themselves).  Of course 
ccache's problem is a bit worse than ours - they cache 3 files for every 
.o file (the .o file itself, gcc stdout, and gcc stderr) while we only 
cache 2 files per ,ko (the .ko itself and the associated .c file).

(Also note that the number of levels is configurable.  The default is 2, 
but setting the SYSTEMTAP_NLEVELS environment variable lets you set it 
from 1 to 8.)

-- 
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)

  reply	other threads:[~2006-10-23 20:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20 18:44 Stone, Joshua I
2006-10-20 19:26 ` David Smith
2006-10-20 19:32   ` Frank Ch. Eigler
2006-10-20 19:50     ` David Smith
2006-10-20 20:13       ` Frank Ch. Eigler
2006-10-23 20:36         ` David Smith [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-25 18:54 Stone, Joshua I
2006-10-26  1:07 ` Frank Ch. Eigler
2006-10-24  0:29 Stone, Joshua I
2006-10-24 15:16 ` David Smith
2006-10-20 20:51 Stone, Joshua I
2006-10-19 20:33 Stone, Joshua I
2006-10-19 20:41 ` David Smith
2006-10-06 19:08 Frank Ch. Eigler
2006-10-06 20:33 ` David Smith
2006-10-06 20:40   ` Frank Ch. Eigler
2006-10-19 19:49     ` David Smith
2006-10-19 21:53       ` Frank Ch. Eigler
2006-10-20 13:50         ` David Smith

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=453D27A8.3050407@redhat.com \
    --to=dsmith@redhat.com \
    --cc=fche@elastic.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).