Re^7: Proper undefine queue with multithreads

The problem here I think is that as soon as the queue gets empty it hits the undefined entries. But after that, new entries are being pushed into the queue but get ignored because the threads were joined already at that time.

Okay. So now we get to the crux of the real question you should have asked: How to determine when there are no more directories to be processed? (And thus, the threads can safely terminate.)

You cannot have the main thread post the undefs once it has finished the initial population of the queue, because the worker threads will be adding to the queue as they process that initial population.

And you cannot use the absence of queue entries (Q->pending == 0), because another thread may add another directory to the queue a millisecond later.

This is the classic chicken & egg scenario. How can any of the worker threads know when they are finished, when at any given moment in time one of the other worker threads might queue an new directory to be processed?

I don't have an answer for you yet. I'm not sure that there is an answer given the current methodology of your code.

I'm sure that there is a better way, and I'll get back to you once I think of it.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re^7: Proper undefine queue with multithreads


Clear questions and runnable code get the best and fastest answer
	PerlMonks