Subj : Re: Hazard Pointers w/o memory barrier.
To   : comp.programming.threads
From : Joe Seigh
Date : Tue Apr 19 2005 04:24 pm

On Tue, 19 Apr 2005 10:31:58 -0700, Chris Thomasson <_no_damn_spam_cristom@_no_damn_comcast.net_spam> wrote:

>> On Solaris and possibly Aix, you can use /proc to get context switching
>> counts
>> for threads to use as quiesce points.  For other unices and Linux, you
>> will need
>> to periodically signal each thread to execute a signal handler that
>> increments
>> a signal count to use as quiesce points.  For windows, there's no
>> asynchronous
>> signal facility or /proc, but there's a hack that will work.  I won't
>> disclose it since
>> I don't support windows and I want to see how long it takes someone else
>> to figure it out.
>
> You can "probably" use GetThreadTimes and check the kernel time for
> per-thread changes. Here is the scheme I have in mind:
>
>
[...]
>
>
>
> What do ya think Joe?
>
> ;)
>
>

Pretty quick.  That's what I spent part of yesterday doing.  Verifying that
Windows had a virtual thread timer that was updated on the fly.  Plus
some time verifying that some Linux and Unix functions were totally useless.

-- 
Joe Seigh

When you get lemons, you make lemonade.
When you get hardware, you make software.

.