Re: Thread Pre-Emption Question . . .

Chris Thomasson wrote:

Your rw-mutex has way too much overhead for read access. You don't need to acquire a lock (e.g., WriterMutex) in your ReadEnter/Leave functions. Here is an example of how you can do it:

http://groups.google.com/group/comp.programming.threads/msg/cfdc3cec444b5544

Oh I see, you wanted to show us YOUR OWN WORK.

Cool.

Unfortunately, I can't trust your work until you can prove your credentials and tell me where do you have this implemented and tested under high loads. What products do you have this implemented in?

Also, what are your TCriticalSection::Check/Count functions used for? Functions like that are usually a sign of poor design. The results you get from those functions are not coherent wrt the current state of the lock at any one time.

Baloney.

The fact our products are used by hundreds of thousands of customer for nearly 12 years under 365x24x7 operating conditions, uncategorically proves without the shadow of a double the HIGH QUALITY of the RPC server/client system with absolutely NO multi-threads contention conflicts.

Now, if you want to show HOW we can run into a problem with an example, I am willing to listen. I'm too old to have regrets and have no problem is there is a potential hidden issue. But I am not going to take YOUR blurted out claims that your CODE is any better or worst. You have to prove it.

--
HLS
.