> DTrace does allow for some very unobtrusive
> observation. Enabling every
> fbt::: probe is always going to have a measurable
> effect on performance.
>
> Rather, I suspect a latent race condition, the window
> for which is
> opened once the code has been slowed down by the
> sledge hammer of
> enabling every fbt probe.
Ok, this should be some race condition.
I get the "error" even with 61 probes enabled only in PCFS (fired 33146 per 10
mkdir iterations in test line).
dtrace -Fn 'syscall::mkdir*:entry { self->trc=1 } syscall::mkdir*:return {
self->trc=0 } fbt:pcfs:pc_*:return /self->trc/ { } ' > /dev/null
I noticed very funny fact if I changedfbt:pcfs:pc_*:return ->
changedfbt:pcfs:pc_*:entry removes the "error".
I am very unhappy :-(
M.C>
--
This message posted from opensolaris.org
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
