Folks,
I'm still trying to resolve NTP on Windows Vista. I do have a dual-core
system, so I was wondering how NTP handled dual-core. Does it discipline
both cores, and is a special start-up switch required? Should I define
the affinity for NTP to a single core?
Looking at the AMD Web site,
David J Taylor wrote:
> Folks,
>
> I'm still trying to resolve NTP on Windows Vista. I do have a dual-core
> system, so I was wondering how NTP handled dual-core. Does it discipline
> both cores, and is a special start-up switch required? Should I define
> the affinity for NTP to a single co
Richard B. Gilbert wrote:
> David J Taylor wrote:
>> Folks,
>>
>> I'm still trying to resolve NTP on Windows Vista. I do have a
>> dual-core system, so I was wondering how NTP handled dual-core. Does
>> it
>> discipline both cores, and is a special start-up switch required?
>> Should I
>> defin
David J Taylor wrote:
[]
> Looking at the AMD Web site, they do have a utility to sync the two
> cores - "AMD Dual-Core Optimizer" - under certain circumstances. I
> tried to install this on Vista, but a file appears to be missing!
Fixed by using "Run as administrator".
Cheers,
David
David,
The multiple-CPU nanokernel code that left here and is in the Alpha
kernel assumes each CPU has an individual cycle counter and the timer
interupts are vectored to a designated CPU. There is a data structure
associated with each CPU that holds the measured current cycle counter
scaling
David L. Mills wrote:
> David,
>
> The multiple-CPU nanokernel code that left here and is in the Alpha
> kernel assumes each CPU has an individual cycle counter and the timer
> interupts are vectored to a designated CPU. There is a data structure
> associated with each CPU that holds the measured c
David J Taylor wrote:
> NTP on Windows uses the RDTSC instruction. Which CPU does it read the
> time stamp counter from? If NTP is multi-threaded, different threads
> could be run on different CPUs with different TSCs. Yes, just the same
> issues arise with 4 CPUs, and I don't know how the W
Dave,
While I would agree with you in general, we don't have any real idea
what the Windows code is doing whether or not it is a uniprocessor or
multiprocessor. I very much doubt that they duplicated your work though
I would think that it's very important for the CPU's to keep each other
in close
Danny Mayer wrote:
> David J Taylor wrote:
>
>> NTP on Windows uses the RDTSC instruction. Which CPU does it read
>> the time stamp counter from? If NTP is multi-threaded, different
>> threads could be run on different CPUs with different TSCs. Yes,
>> just the same issues arise with 4 CPUs, and
David J Taylor wrote:
> Danny Mayer wrote:
>
>>David J Taylor wrote:
>>
>>
>>>NTP on Windows uses the RDTSC instruction. Which CPU does it read
>>>the time stamp counter from? If NTP is multi-threaded, different
>>>threads could be run on different CPUs with different TSCs. Yes,
>>>just the sam
Richard B. Gilbert wrote:
[]
> Have you considered disabling Windows Vista?? ;-)
>
> Linux or Solaris X86 should do a far better job of keeping time than
> Windows.
Richard,
You may well be right, but there are many people today who need Windows
for the applications they wish to run, so altern
On Dec 1, 8:58 am, "David J Taylor" <[EMAIL PROTECTED]
bit.nor-this-bit.co.uk> wrote:
> Richard B. Gilbert wrote:
> > David J Taylor wrote:
> >> Folks,
>
> >> I'm still trying to resolve NTP on Windows Vista. I do have a
> >> dual-core system, so I was wondering how NTP handled dual-core. Does
>
On Dec 1, 10:42 am, "David L. Mills" <[EMAIL PROTECTED]> wrote:
> The multiple-CPU nanokernel code that left here and is in the Alpha
> kernel assumes each CPU has an individual cycle counter and the timer
> interupts are vectored to a designated CPU. There is a data structure
> associated with ea
David J Taylor wrote:
> Danny Mayer wrote:
>> David J Taylor wrote:
>>
>>> NTP on Windows uses the RDTSC instruction. Which CPU does it read
>>> the time stamp counter from? If NTP is multi-threaded, different
>>> threads could be run on different CPUs with different TSCs. Yes,
>>> just the same
Danny Mayer wrote:
> David J Taylor wrote:
[]
>> Thanks for your reply. Perhaps my recollection is at fault here,
>> but I recall that NTP on Windows uses some interpolation technique
>> to overcome timer granularity, and that the interpolation used a CPU
>> counter.
>
> We are intending to implem
Guys,
David J Taylor wrote:
> The Windows implementation does try to provide granularity within the
> tick, but I have no idea how the Meinberg port I'm using handles
> multi-processors. Checking. I see the routine: nt_clockstuff.c mentions
> that how to handle multi-processors is not yet decide
Martin Burnicki wrote:
[]
> I think a few notes are required here.
>
> The ntpd port for Windows does interpolate (or extrapolate?) between
> the timer ticks. This has been in the NTP code base for a long time
> and has _not_ been invented by Meinberg. And, just to recall, there
> is no "Meinberg p
Danny Mayer wrote:
> David J Taylor wrote:
>> Thanks for your reply. Perhaps my recollection is at fault here, but I
>> recall that NTP on Windows uses some interpolation technique to overcome
>> timer granularity, and that the interpolation used a CPU counter.
>
> We are intending to implement t
David J Taylor wrote:
>> There is one other thing that needs to be considered. This is a 64-bit
>> system> In that case it's possible that the code may need to be
>> changed to deal with it properly. For example using the VS 2005
>> compiler I have found that it uses a 64-bit integer instead of 32-
Martin Burnicki wrote:
> Guys,
>
> David J Taylor wrote:
>> The Windows implementation does try to provide granularity within the
>> tick, but I have no idea how the Meinberg port I'm using handles
>> multi-processors. Checking. I see the routine: nt_clockstuff.c mentions
>> that how to handle m
Martin Burnicki wrote:
> Danny Mayer wrote:
>> David J Taylor wrote:
>>> Thanks for your reply. Perhaps my recollection is at fault here, but I
>>> recall that NTP on Windows uses some interpolation technique to overcome
>>> timer granularity, and that the interpolation used a CPU counter.
>> We a
Danny Mayer wrote:
[]
> With VS 2005, just open the dsw file and tell it to convert all the
> project files. I recently add the necessary macros to the dsp files so
> that I don't have to add a bunch of macros every time I pull in a new
> tarball. I'm only building on VS 2005 these days. Building o
Danny,
Danny Mayer wrote:
> David J Taylor wrote:
>> The version I'm testing is the 32-bit version of Vista, albeit on a
>> 64-bit
>> capable CPU. 64-bit can be a pain though for subtle errors, I
>> appreciate.
>>
>
> That's a problem. There are even more subtle issues when you run a
> 32-bit O
David,
David J Taylor wrote:
> Martin Burnicki wrote:
>> While on legacy multiprocessor systems the CPU clocks (and thus the
>> TSC) may differ for each CPU, I'm _assuming_ that multicore CPUs are
>> clocked by the same source, so the TSCs should runs synchrounously.
>
> This assumption is probab
Martin Burnicki wrote:
> Danny,
>
> Danny Mayer wrote:
>> David J Taylor wrote:
>>> The version I'm testing is the 32-bit version of Vista, albeit on a
>>> 64-bit
>>> capable CPU. 64-bit can be a pain though for subtle errors, I
>>> appreciate.
>>>
>>
>> That's a problem. There are even more subtl
Martin Burnicki wrote:
[]
> I've just set up a new test under Vista, so let's see.
>
> What I can say right now is that the default tick adjustment value is
> 156001 instead of 156250 which it used to be on earlier Windows
> versions. Also the granularity of the system clock has changed from
> 15.6
Evandro,
Yes, the nanocode is aware that individual CPU clock rates can differ
and vary over time. Since the only purpose is to interpolate between
timer interrupts (Alpha) or second overflows (FreeBSD), all the code
does is count the number of PCC cycles since the last interrupt to
construct
David,
David J Taylor wrote:
> Martin Burnicki wrote:
> []
>> I've just set up a new test under Vista, so let's see.
>>
>> What I can say right now is that the default tick adjustment value is
>> 156001 instead of 156250 which it used to be on earlier Windows
>> versions. Also the granularity of t
Martin Burnicki wrote:
> David,
[]
> I had made a fresh installation of Vista and forgot to disable
> automatic sleep mode, so my overnight test failed and I had to run it
> once more over the last hours.
Been there, done that!
> The test machine is a Intel Pentium D 3 GHz (dual core) with Window
David J Taylor wrote:
> Danny Mayer wrote:
> []
>> With VS 2005, just open the dsw file and tell it to convert all the
>> project files. I recently add the necessary macros to the dsp files so
>> that I don't have to add a bunch of macros every time I pull in a new
>> tarball. I'm only building on
Martin Burnicki wrote:
>
> Hm, the process CPU affinity is not restricted to a single CPU. Ntpd has 4
> active threads, and only the CPU affinity of the clock interpolation thread
> is restricted to the first CPU since this is the only thread which calls
> QueryPerformanceCounter() and thus potent
Danny Mayer wrote:
[]
> You need to run the OpenSSL build first to create that directory. Just
> follow the instructions.
>
> Danny
Danny,
I'm afraid the build didn't work for me, so I tried creating a directory
"openssl" in the ntp tree, and copied 33 header files from the OpenSSL
tree. Havin
Hi Ulrich,
Ulrich Windl wrote:
> Martin Burnicki <[EMAIL PROTECTED]> writes:
>
> [...]
>> The test machine is a Intel Pentium D 3 GHz (dual core) with Windows
>> Vista x64. Data of the time synchronization performance was collected by
>> the time adjustment service which comes with the Meinberg d
David,
David J Taylor wrote:
> I find it difficult to judge the results in comparison with mine as the
> timescales cover a rather different range, but the message is clear -
> under Vista (your 64-bit or my 32-bit) timekeeping with NTP is orders of
> magnitude worse than it should be. It might b
David L. Mills wrote:
> David,
>
> Don't look in the NTP distribution for interpolation code; that's in
> the kernel, for the Alpha the nanokernel code. All the code there, by
> the way, is in C for portability. By the way, I see that code is no
> longer available via http, only anonymous ftp.
>
>
David,
Don't look in the NTP distribution for interpolation code; that's in the
kernel, for the Alpha the nanokernel code. All the code there, by the
way, is in C for portability. By the way, I see that code is no longer
available via http, only anonymous ftp.
Dave
David J Taylor wrote:
> Dav
Martin Burnicki wrote:
[]
> There's now a new graph recorded under 32 bit Vista:
> http://www.meinberg.de/download/ntp/graphs/ntp-dev-4.2.5p104-windows-vista-32.pdf
>
> The first section is with maxpoll 6, and in the second part maxpoll
> has been reduced to 4, which does not seem to eliminate the
Martin Burnicki <[EMAIL PROTECTED]> writes:
[...]
> The test machine is a Intel Pentium D 3 GHz (dual core) with Windows Vista
> x64. Data of the time synchronization performance was collected by the time
> adjustment service which comes with the Meinberg driver package for
> Windows. That service
David J Taylor wrote:
> David L. Mills wrote:
>> David,
>>
>> Don't look in the NTP distribution for interpolation code; that's in
>> the kernel, for the Alpha the nanokernel code. All the code there, by
>> the way, is in C for portability. By the way, I see that code is no
>> longer available via
Martin Burnicki wrote:
[]
> David (J. Taylor),
>
> Please take care. You and Dave (L. Mills) are talking about completely
> different things here.
[]
> Martin
Thanks, Martin. Yes, I'm aware of the difference, but as both topics
currently have the same name the source of the confusion remains. P
On Dec 3, 2:28 pm, "David L. Mills" <[EMAIL PROTECTED]> wrote:
> Yes, the nanocode is aware that individual CPU clock rates can differ
> and vary over time. Since the only purpose is to interpolate between
> timer interrupts (Alpha) or second overflows (FreeBSD), all the code
> does is count the n
David J Taylor wrote:
> Danny Mayer wrote:
> []
>> You need to run the OpenSSL build first to create that directory. Just
>> follow the instructions.
>>
>> Danny
>
> Danny,
>
> I'm afraid the build didn't work for me, so I tried creating a directory
> "openssl" in the ntp tree, and copied 33 hea
Danny Mayer wrote:
[]
> No, you extract the openssl files to a directory at the same level as
> ntp. Then you read the INSTALL.W32 file for instructions on how to
> build openssl. I don't build with the assembler code.
Danny, thanks for your "encouragement" - I did do all this, of course, but
I w
Danny,
I have tried to follow the build instructions, but they fail at the
command:
call ms\do_ms
at the line:
___
D:\Temp\NTP\openssl-0.9.8g.tar\openssl-0.9.8g>perl util\mk1mf.pl no-asm
VC-CE 1
>ms\ce.mak
%OSVERSION% is not defined at util/pl/VC-32.pl line
>>> In article <[EMAIL PROTECTED]>, "David J Taylor" <[EMAIL PROTECTED]> writes:
David> That error, perhaps, but there are dozens of warnings when you
David> compile, making it impossible to judge what success you have had. I
David> come from a background where we expect software to compile with
David J Taylor wrote:
> Danny Mayer wrote:
> []
>
>>No, you extract the openssl files to a directory at the same level as
>>ntp. Then you read the INSTALL.W32 file for instructions on how to
>>build openssl. I don't build with the assembler code.
>
>
> Danny, thanks for your "encouragement" - I
Richard B. Gilbert wrote:
[]
> That can be extremely difficult to achieve over multiple platforms and
> compilers.
Multi-platform must make zero warnings many times more difficult - I can
appreciate that.
> It is made more difficult because various compiler accept different
> deviations from the
David J Taylor wrote:
> Richard B. Gilbert wrote:
> []
>
>>That can be extremely difficult to achieve over multiple platforms and
>>compilers.
>
>
> Multi-platform must make zero warnings many times more difficult - I can
> appreciate that.
>
>
>>It is made more difficult because various comp
David J Taylor wrote:
> That error, perhaps, but there are dozens of warnings when you compile,
> making it impossible to judge what success you have had. I come from a
> background where we expect software to compile with a "zero errors, zero
> warnings" result.
>
I don't work on OpenSSL or
Harlan Stenn wrote:
In article <[EMAIL PROTECTED]>, "David J Taylor" <[EMAIL PROTECTED]>
writes:
>
> David> That error, perhaps, but there are dozens of warnings when you
> David> compile, making it impossible to judge what success you have had. I
> David> come from a background where
David J Taylor wrote:
> Danny,
>
> I have tried to follow the build instructions, but they fail at the
> command:
>
> call ms\do_ms
>
Start from the beginning. Delete everything and then reexport the
compressed tar file. The top-level directory (openssl-0.9.8g) should be
at the same level as
Richard B. Gilbert wrote:
> David J Taylor wrote:
>> Danny Mayer wrote:
>> []
>>
>>> No, you extract the openssl files to a directory at the same level as
>>> ntp. Then you read the INSTALL.W32 file for instructions on how to
>>> build openssl. I don't build with the assembler code.
>>
>> Danny, th
Danny Mayer wrote:
> Richard B. Gilbert wrote:
>
>>David J Taylor wrote:
>>
>>>Danny Mayer wrote:
>>>[]
>>>
>>>
No, you extract the openssl files to a directory at the same level as
ntp. Then you read the INSTALL.W32 file for instructions on how to
build openssl. I don't build with the
Danny Mayer wrote:
[]
> Start from the beginning. Delete everything and then reexport the
> compressed tar file. The top-level directory (openssl-0.9.8g) should
> be at the same level as the version of NTP that you are going to use.
>
> Run the following lines at the command-line prompt when you ha
David J Taylor wrote:
> Danny Mayer wrote:
> []
>> Start from the beginning. Delete everything and then reexport the
>> compressed tar file. The top-level directory (openssl-0.9.8g) should
>> be at the same level as the version of NTP that you are going to use.
>>
>> Run the following lines at the
Danny Mayer wrote:
[]
> No. I don't know why there's a tar directory involved here. I don't
> use temp at all. My structure would look like (well you don't really
> want to look at my structures since they are bizarre at best):
>
> D:\ntp-4.2.4p4\
> D:\openssl-0.9.8g\
OK, I tried with those direct
56 matches
Mail list logo
