RE: pthread_cond_timedwait accurate to one second only

RE: pthread_cond_timedwait accurate to one second only

[Thomas Pfaff]

 > 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.

This is already fixed. Try the snapshot.
Bit do not expect that you can use it with 10 ms delays. Windows is not 
a realtime system.

Thomas


--
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/

RE: pthread_cond_timedwait accurate to one second only

[Hannu E K Nevalainen (garbage mail)]

> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.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/

Re: pthread_cond_timedwait accurate to one second only

[Timothy C Prince]

-----Original Message-----
From: "peter garrone" <pgarrone@linuxmail.org>
To: cygwin@cygwin.com
Date: Mon, 25 Aug 2003 15:42:52 +0800
Subject: pthread_cond_timedwait accurate to one second only

Hi.
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 order to avoid going to newlib and implementing Windows GetLocalTime() calls in gettimeofday(), we made the -mwin32 build option invoke the API milliseconds call directly in the g77 runtime libf2c/libU77/datetime_.c.  I think the "inherent reason" is the perceived awkwardness in making <sys/time.h> library calls pick up milliseconds on Windows, while leaving the lower order part of the microseconds field undetermined.  My documentation on ftime() says it is obsoleted by gettimeofday().
Tim Prince

--
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/

pthread_cond_timedwait accurate to one second only

[peter garrone]

Hi.
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?
-- 
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr

Powered by Outblaze

--
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/