This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Is eCos having this constrains


Hi 

I have some doubt, 
How many number of mutex you can initialize in your single project while using eCos . Is there any limitation other than memory constrains. I am talking about this memory constrains, since at the time of initializing the mutex the OS will allocate a memory for a queue (which will maintain the status of threads), and the queue size is depend upon the number of task using the same mutex variable.
Is my thinking is on right track. If its so than 
****How many no of mutex variable you can initialize and use in single project.
****How many task can used the same mutex variable in order to resolve shared resource problem.
Is eCos having this constrains or POSIX is providing any guidelines for this.

Please let me know your valuable suggestions.

Regards
Prabhat Shrivastav





--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]