From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16824 invoked by alias); 30 Jan 2003 01:44:41 -0000 Mailing-List: contact pthreads-win32-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sources.redhat.com Received: (qmail 16807 invoked from network); 30 Jan 2003 01:44:40 -0000 Received: from unknown (HELO digit.ise.canberra.edu.au) (137.92.140.41) by 172.16.49.205 with SMTP; 30 Jan 2003 01:44:40 -0000 Received: from ise.canberra.edu.au (localhost.localdomain [127.0.0.1]) by digit.ise.canberra.edu.au (8.12.5/8.12.5) with ESMTP id h0U1n1cA018559; Thu, 30 Jan 2003 12:49:02 +1100 Message-ID: <3E38848D.1050705@ise.canberra.edu.au> Date: Thu, 30 Jan 2003 01:44:00 -0000 From: Ross Johnson Organization: University of Canberra, Management and Technology User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthew Ford CC: pthreads-win32@sources.redhat.com Subject: Re: Which thread is released when pthread_cond_signal() is called References: <007a01c2c7f1$9238d8c0$0200a8c0@NOTEBOOK> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003/txt/msg00016.txt.bz2 In pthreads-win32 this will be determined by the behaviour of Win32's WaitForMultipleObjects() and ReleaseSemaphore() routines, which are at the centre of pthread_cond_*(). I think Win32 semaphore releases are FIFO, like Win32 mutexes. Ross Matthew Ford wrote: > Assume for simplicity that all the waiting threads are of the same > priority. > Which one will wake up on a call to > pthread_cond_signal() > > regards > matthew