From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] dtrace for plan 9
Date: Mon, 9 Nov 2009 07:45:39 -0800 [thread overview]
Message-ID: <13426df10911090745x3a64152dsac5ce91fc76db4e6@mail.gmail.com> (raw)
In-Reply-To: <fcf97221ebe434e15a5704aa84f94f78@brasstown.quanstro.net>
On Mon, Nov 9, 2009 at 6:28 AM, erik quanstrom <quanstro@quanstro.net> wrote:
> with devtrace, the situation is the opposite. jitter is
> important (to eliminate), 541 small fixed-sized events can
> be returned per system call and there is one trace device
> per system.
Note that we can filter on up to 16 PIDs already. Also, you can grow
the buffer space to 256 KB -- but yes, we could grow it further.
I'd be glad to hear we don't need more complex kernel support for
devtrace. User mode is my favorite place to filter. But, that said,
putting in a simple min/max test for the params would be simple.
Anyway, we'll work on seeing what we need.
ron
next prev parent reply other threads:[~2009-11-09 15:45 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<13426df10911081656q75a7b5aawd01dc9df71beca08@mail.gmail.com>
2009-11-09 14:28 ` erik quanstrom
2009-11-09 15:45 ` ron minnich [this message]
2009-11-09 16:01 ` erik quanstrom
[not found] <<9ab217670911091908u25e0a23bk838bd67c460492ac@mail.gmail.com>
2009-11-10 3:26 ` erik quanstrom
2009-11-10 4:05 ` Devon H. O'Dell
[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] <<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
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] <<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=13426df10911090745x3a64152dsac5ce91fc76db4e6@mail.gmail.com \
--to=rminnich@gmail.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).