Re: micro-optimization
- From: Dave Hart <davehart@xxxxxxxxx>
- Date: Wed, 11 Mar 2009 10:09:52 -0700 (PDT)
On Mar 11, 8:55 am, Martin Burnicki <martin.burni...@xxxxxxxxxxx>
wrote:
Dave Hart wrote:
I have released a new test version of 4.2.4p6 with numerous Windows-
specific improvements compared to the baseline 4.2.4p6. Since my last
release, the most significant change is to read the processor cycle
counter using the RDTSC instruction directly when it is equivalent to
QueryPerformanceCounter. When it is not equivalent, ntpd is allowed
to roam freely across all logical processors once again.
As a consequence of the above I'd say using RDTSC directly instead of QPC is
a step in the wrong direction. From what I've seen adding the /usepmtimer
switch should fix problems on systems where TSC is used even though it is
not reliable.
This should also make it obsolete to nail down all threads to a single CPUm
as suggested in bug #1124:https://support.ntp.org/bugs/show_bug.cgi?id=1124
Or am I missing something?
I think so. This version only uses RDTSC if QueryPerformanceCounter
is using RDTSC. If the HAL is using a different timer for QPC, this
version uses QPC.
Regarding bug 1124 with this version threads are not nailed down to a
particular processor except when RDTSC underlies QPC.
Cheers,
Dave Hart
.
- Follow-Ups:
- Re: micro-optimization
- From: Martin Burnicki
- Re: micro-optimization
- References:
- micro-optimization
- From: Dave Hart
- Re: micro-optimization
- From: Martin Burnicki
- micro-optimization
- Prev by Date: Re: ntpd -x option
- Next by Date: Re: best gps receiver for time synchronization
- Previous by thread: Re: micro-optimization
- Next by thread: Re: micro-optimization
- Index(es):
Relevant Pages
|