Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Hannu E K Nevalainen \(garbage mail\)" To: Subject: RE: pthread_cond_timedwait accurate to one second only Date: Mon, 25 Aug 2003 20:49:13 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal In-Reply-To: <20030825074253.3769.qmail@linuxmail.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 > From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf > Of peter garrone > I would like to use this function down to 10 milliseconds > accuracy if possible. > However upon looking at winsup/cygwin/thread.cc, > it uses the function "ftime" and the millisecond field is ignored. > > All the examples in the winsup testsuite also generally check to > 5 seconds only. > > Is there any inherent reason why finer timing would not work? In general; You're asking for RTOS granularity from a desktop OS. Desktop OS'es in general allows that accuracy only in theoretical terms. This might very well be the sole reason. Expect even less accuracy from Cygwin; because it is a partly emulated environment. NOTE: not saying to which degree here... I simply do not know. /Hannu E K Nevalainen, B.Sc. EE Microcomputer systems - 59°16.37'N, 17°12.60'E --END OF MESSAGE-- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/