Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 9 May 2002 12:04:49 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [PATCH] gettimeofday time travels
Message-ID: <20020509160449.GF6910@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <15547 DOT 16136 DOT 163472 DOT 840007 AT bea DOT com> <20020415214133 DOT GA19612 AT redhat DOT com> <15577 DOT 12319 DOT 622365 DOT 566799 AT bea DOT com> <20020508144104 DOT GA1093 AT redhat DOT com> <15578 DOT 30482 DOT 568575 DOT 767214 AT bea DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <15578.30482.568575.767214@bea.com>
User-Agent: Mutt/1.3.23.1i

On Thu, May 09, 2002 at 02:18:10PM +0100, Philip Aston wrote:
>I the decision is now a question of efficiency. My approach is
>simpler, and it means we don't have to call both
>QueryPerformanceCounter and GetSystemTime every time. It also means we
>don't have to do arithmetic to get the result of GetSystemTime in some
>form in which it can be compared to our QueryPerformanceCounter
>calculation.
>
>I can't see any other reason to pick ChrisJ's method over mine?
>
>Thoughts anyone...?

An NT only solution is not a solution.

Syncing every "x" seconds also is not a solution.

The correct solution is to resync after events which cause the clock to
stop.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/