On Apr 5, 2009, at 2:47 AM, Michael Mueller wrote:
So does this mean that accessing aggregations is guaranteed to be
thread
safe? Does this also apply to accessing associative arrays?
Yes, aggregations are scalable and thread-safe. One thing we've
considered
adding is some sort of
Are associative arrays thread-safe as well? For example
a[some-string] += 1;
Michael
Adam Leventhal wrote:
On Apr 5, 2009, at 2:47 AM, Michael Mueller wrote:
So does this mean that accessing aggregations is guaranteed to be thread
safe? Does this also apply to accessing associative
Hi Angelo,
One of my ISVs have been looking for the atomic operation for global
variables as well. While we wait for this feature, do you have any
ideas for a reasonably good work around, now?
There isn't an RFE for this; if there is a need (or a perceived need)
then please log an RFE on
On Mon, Apr 06, 2009 at 10:27:59AM +0200, Michael Mueller wrote:
Are associative arrays thread-safe as well? For example
a[some-string] += 1;
No; they act just like global variables.
Cheers,
- jonathan
Michael
Adam Leventhal wrote:
On Apr 5, 2009, at 2:47 AM, Michael Mueller
On Mon, Apr 06, 2009 at 08:55:03AM -0700, Jonathan Adams wrote:
On Mon, Apr 06, 2009 at 10:27:59AM +0200, Michael Mueller wrote:
Are associative arrays thread-safe as well? For example
a[some-string] += 1;
No; they act just like global variables.
i.e. because they are global
Is proc:::start expected to fire before the first instruction of an
exec'd process is executed, or
only on new (processes with a different pid) processes?
James M
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
Is proc:::start expected to fire before the first instruction of an
exec'd
process is executed, or
only on new (processes with a different pid) processes?
Hey James,
proc:::start only fires with new processes that are forked. The proc:::exec
probe tracks exec-related activities.
