On Thu, 24 May 2012 10:09:45 +0000 (GMT) SHILPA ONKAR SINGH <shilpa.si...@samsung.com> said:
pedantic! :-P :) ok ok > not >= - makes no material difference :) > Thanks for the fix, > but a trivial error I noticed in ecore_thread_max_set > first a check is added to see whether num >= 16*eina_cpu_count > and then num = 16*eina_cpu_count > instead the check has to be num > 16*eina_cpu_count > > Thanks & Regards > Shilpa > > > ------- Original Message ------- > Sender : Carsten Haitzler<ras...@rasterman.com> > Date : May 24, 2012 18:58 (GMT+09:00) > Title : Re: [E-devel] Elementary+threading > > On Wed, 23 May 2012 20:13:24 +0200 Leif Middelschulte > said: > > it seems cedric loves to starve the workers. never let cedric be in charge > man... just think. you'll be starving. :) seriously - the thread workers did > this: > > while (queue_a) handle(queue_a); > while (queue_b) handle(queue_b); > > normal ecore-thread workers are on queue a... ecore-thread FEEDBACK workers > are on queue b. this means as your workers keep re-scheduling themselves in a > tight loop queue a is ALWAYS full and busy and queue b never gets a turn. > fileselector uses eio. eio uses both thread AND thread feeback workers. thus > its tasks for queue b were being held "pending" forever due to your > pathological re-scheduling workers. > > i've fixed this in svn now and now everyone gets a turn. but remember this. if > you care WHEN your thread is run - then ONLY use ecore-thread FEEDBACK workers > and set the "create a thread" flag to true. this says "i must really have a > thread for this and not make use of the thread pool like everyone else". > otherwise your thread goes into the thread pool to get an available worker > WHEN one becomes available. that may happen at any time in the future - > depending on how many things are in the queue. > > > 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 > > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) ras...@rasterman.com > > > ------------------------------------------------------------------------------ > 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 > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
