Single vs. multi threaded Resource Manager

bridged with qnx.rtos
Post Reply
Polczer Eszter

Single vs. multi threaded Resource Manager

Post by Polczer Eszter » Mon Jan 26, 2004 8:49 am

Hi all!

What is the main difference between a sinlgle and a multi thread Resource
Manager in usage? Can multiple clients use the single thread RM, too? Is
there any rule for that?

Thanks,

Polczer Eszter

Alain Bonnefoy

Re: Single vs. multi threaded Resource Manager

Post by Alain Bonnefoy » Mon Jan 26, 2004 12:03 pm

Polczer Eszter a écrit:
Hi all!

What is the main difference between a sinlgle and a multi thread Resource
Manager in usage?

Hum,
Mainly the block state !?
If you have a single thread resmgr, all clients attempting to access it
will be send blocked. If you have a multi-threaded resmgr, they will be
blocked on a condvar.
This condvar is in fact protecting the attribute structure. If you are
sure to do nothing in the attribute structure of your resmgr, you can do
an 'resmgr_attr_unlock()', this will allow other clients to gain access.
This is potentially dangerous.

I you have declared several names (resmgr_attach()) a thread pool is
helpfull. several clients could access the different resmgr
simultaneously but all clients accessinf the same name will be send blocked.
Can multiple clients use the single thread RM, too? Is
there any rule for that?


As I explained above.
Thanks,

Polczer Eszter



Post Reply

Return to “qnx.rtos”