Todd just pointed out that I had said milliseconds in my lastemail.. The
macro i sent out gives NANOseconds. thats why get_nstime.
Sorry about all the confusion :}
manoj
PS:
rdtsc instruction returns a long long value of the number of ticks from
last hard reboot. Since I have a ppro 200Mhz... multiplying the vlaue by 5
gives the nanoseconds from last reboot. This value ofcourse wont be the
correct nanoseconds in absolute time, since there is bound to be some
drift in the clock. I am currently using just one machine, so i dont care
about the drift.
==============================================================================
_|_
MANOJ APTE -----------(o)----------- 500 Louisville St, #59
High Performance Computing Lab Starkville, MS 39759
phone: (601) 325 7503 phone: (601) 323 8160
Engineering Research Center. email: [EMAIL PROTECTED]
phone: (601) 325 2476 http://www.erc.msstate.edu/~manoj
==============================================================================
> Sent: Friday, March 26, 1999 5:42 PM
> To: Gearheart, Todd
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: [rtl] Digital flight simulator...
>
>
> I use this macro to compute the time. I have a pentium pro 200, so I do
> a multiply by 5 to get the time in milliseconds from the ticks returned
by
> rdtsc. So its a lil more expensive than doing a simple rdtsc. The cpuid
> call is to flush the pipeline before rdtsc, to serialize.
>
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
