Hi, I also tested this behavior recently and checked the ecore - code as well the maximum number of threads that can be spawned equals the cpu count [ Probably design decision ] eina_cpu_count gives the number of CPU and based on which the maximum threads spawned at a time is restricted in code itself. for eg: if I have 1 cpu then I can spawn only one other thread. even If I call ecore_thread_max_set and set higher number of threads no use because of this restriction.
I think we can keep the default thread count based on cpu count but if we call max_set we should be able to increase the number of maximum spawned threads despite of number of CPUs ofcourse some restriction can be put there as well. Please let me know your opinion. Thanks Shilpa ------- Original Message ------- Sender : Leif Middelschulte<[email protected]> Date : May 24, 2012 03:13 (GMT+09:00) Title : [E-devel] Elementary+threading Hey there, I put together an example that reveils unexpected elm behavior here on my T60 (Intel T2500). I'm mentioning my cpu, because - according to ecore_thread's docs - the number of maximum threads is limited to 2n | n = |processors|. For some reason though the default number of threads equals my # of cpus. So anybody who has a more recent machine please extend the number of events emited/threads generated to the number of your maximum threads - 1 to make elm_fileselector show nothing. I hope I'm doing something wrong here. -- Leif ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
