CODEWITHSUNDEEP
c#.netmultithreadingpinvoke
Jeff Cyr
Jeff Cyr

Reputation: 4864

.Net How to get notified efficiently when a thread is suspended?

Does anyone know a way to get notified when a specific thread is being suspended and resumed?

I would like to be able to to something like this:

thread.Suspended += delegate
{
    //Do something
};

thread.Resumed += delegate
{
    //Do something else
};

I doubt that the .Net Framework has this capability, but is there a technique to achieve this maybe with pinvoke? I need it to be possible with low overhead.

Upvotes: 0

Views: 308

Answers (2)

donovan
donovan

Reputation: 1472

If you're committed to writing your own thread pool this probably doesn't help, but I'd try to stick with the .NET ThreadPool class and tune it as required with SetMaxThreads/SetMinThreads and GetMaxThreads/GetAvailableThreads. Is there any particular reason why this isn't good enough?

I was at PDC last year and attended some of Joe Duffy's talks on parallelism were quite interesting. I recall he was talking about providing an extensible thread pool class in .NET since MSFT generally find that when people go and write their own thread pools they'll work fine most of the time, but get caught out in edge cases by various gotchas. By providing an extensibility mechanism they were hoping to limit the potential for devs to get caught out.

Upvotes: 2

Michael
Michael

Reputation: 55415

Windows has no such notification mechanism for Thread.Suspend/Thread.Resume You should not be using Thread.Suspend/Thread.Resume - it can easily lead to deadlocks and other hard to find bugs. Use the normal synchronization primitives (locks, events, etc.) to cause a thread to block until it has work to do.

UPDATE:

You could enable context switch events in ETW and consume them via ProcessTrace. OldThreadId and OldThreadState will tell why a thread stopped running (transition to ready, standby, waiting, etc., etc.). NewThreadId will tell you when a thread starts running. You will have to process events for every context switch in the system. It will be incredibly high volume, consume a lot of CPU in your process, and be very difficult to get precisely right.

Upvotes: 0

Related Questions