From: dave.l@mac.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] dtrace for plan 9
Date: Fri, 13 Nov 2009 23:47:38 +0000 [thread overview]
Message-ID: <045076EF-2053-42B5-A2DD-844E9577D35E@mac.com> (raw)
In-Reply-To: <e763acc10911101538q781643a0u6a79bafcd3e4f183@mail.gmail.com>
> Would this answer your question:
> http://blogs.sun.com/jonh/entry/the_dtrace_deadman_mechanism
Well, it answers the question "What is the DTrace so-called deadman
mechanism?" I think.
That's a sort of part of a possible solution, which is OK.
To be pedantic, it's not a true deadman mechanism,
which operates at the point of failure (incapacity of the driver), not
when it's all over (death of the passengers).
What's described there is more like a pair of buffers at the end of
the crowded terminus station.
> Or are you literally trying to figure out the upper bound on the # of
> virtual instructions
> in a single probe?
Well, more importantly, the consequent real-time involved.
IOW: assuming you have some common sense (and a degree of chutzpah,
given the complexity of the solaris kernel),
and thus you have a reasonable idea about how long a time "too long"
is to be holding up your kernel,
how do you know whether a given D bytecode blob is gonna execute for
"too long" or not?
D
next prev parent reply other threads:[~2009-11-13 23:47 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<9ab217670911010852h46cc32a0k2e3ef99323287595@mail.gmail.com>
2009-11-01 16:58 ` erik quanstrom
2009-11-01 18:44 ` Nathaniel W Filardo
2009-11-03 15:30 ` Iruata Souza
2009-11-03 18:29 ` Lyndon Nerenberg
2009-11-03 18:50 ` Iruata Souza
2009-11-07 10:45 ` Ethan Grammatikidis
2009-11-07 17:44 ` ron minnich
2009-11-08 14:19 ` dave.l
2009-11-09 0:07 ` dave.l
2009-11-09 0:27 ` hiro
2009-11-09 0:56 ` ron minnich
2009-11-10 0:33 ` Nathaniel W Filardo
2009-11-10 0:46 ` ron minnich
2009-11-10 1:00 ` Roman Shaposhnik
2009-11-10 20:21 ` dave.l
2009-11-10 23:38 ` Roman Shaposhnik
2009-11-13 23:47 ` dave.l [this message]
2009-11-10 2:37 ` erik quanstrom
2009-11-10 3:08 ` Devon H. O'Dell
2009-11-10 4:20 ` Roman Shaposhnik
2009-11-10 0:47 ` Roman Shaposhnik
[not found] <<9ab217670911091908u25e0a23bk838bd67c460492ac@mail.gmail.com>
2009-11-10 3:26 ` erik quanstrom
2009-11-10 4:05 ` Devon H. O'Dell
[not found] <<13426df10911081656q75a7b5aawd01dc9df71beca08@mail.gmail.com>
2009-11-09 14:28 ` erik quanstrom
2009-11-09 15:45 ` ron minnich
2009-11-09 16:01 ` erik quanstrom
[not found] <<Pine.BSI.4.64.0911011858540.4700@malasada.lava.net>
2009-11-02 5:03 ` erik quanstrom
2009-11-02 15:59 ` David Leimbach
[not found] <<4AEDB3DD.2010205@maht0x0r.net>
2009-11-01 16:19 ` erik quanstrom
2009-11-01 16:52 ` Devon H. O'Dell
2009-11-01 17:19 ` ron minnich
[not found] <<e763acc10910312200k4fe66aa8q557dcfe3a1d73ff3@mail.gmail.com>
2009-11-01 13:25 ` erik quanstrom
2009-11-01 16:14 ` matt
2009-11-02 4:59 ` Tim Newsham
[not found] <<13426df10910271720t7679d169k84fb7d4b9a9cefc5@mail.gmail.com>
2009-10-28 1:49 ` erik quanstrom
2009-10-28 2:23 ` ron minnich
2009-10-28 2:38 ` Jeff Sickel
2009-11-01 3:01 ` dave.l
2009-11-01 3:26 ` ron minnich
2009-11-01 5:00 ` Roman Shaposhnik
2009-10-28 0:20 ron minnich
2009-10-28 0:52 ` Devon H. O'Dell
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=045076EF-2053-42B5-A2DD-844E9577D35E@mac.com \
--to=dave.l@mac.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).