From: "Nate Jenkins" <nate@uniwest.com>
To: Ankit Jain <ankitjain1580@yahoo.com>,
linux prg <linux-c-programming@vger.kernel.org>
Subject: Re: nanosecond accuracy
Date: Tue, 28 Sep 2004 10:58:42 -0700 [thread overview]
Message-ID: <001201c4a584$cb40bc60$0100a8c0@Nate> (raw)
In-Reply-To: 000301c4a583$65cae0f0$0100a8c0@Nate
Sorry,
Bad link. The correct link is now
http://www.fsmlabs.com/products/openrtlinux/
Nate
----- Original Message -----
From: "Nate Jenkins" <nate@uniwest.com>
To: "Ankit Jain" <ankitjain1580@yahoo.com>; "linux prg"
<linux-c-programming@vger.kernel.org>
Sent: Tuesday, September 28, 2004 10:48 AM
Subject: Re: nanosecond accuracy
>
> Linux is not a real time operating system and it cannot guaranty that kind
> of accuracy. Look at RTL (Real Time Linux) I am not sure about how finite
> they can get, but I know its better than the millisecond arena...
> http://rtl.org
>
> Nate
>
>
>
>
>
>> if somebody can tell how to find out the time
>> difference in nanosecond
>>
>> i know a struct timerspec which have time in
>> nanosecond but how to use it and there is anyother way
>> out?
>>
>> thanks
>>
>> ankit
>>
>> ________________________________________________________________________
>> Yahoo! Messenger - Communicate instantly..."Ping"
>> your friends today! Download Messenger Now
>> http://uk.messenger.yahoo.com/download/index.html
>> -
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-c-programming" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2004-09-28 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 17:16 nanosecond accuracy Ankit Jain
2004-09-28 17:48 ` Nate Jenkins
2004-09-28 17:58 ` Nate Jenkins [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001201c4a584$cb40bc60$0100a8c0@Nate' \
--to=nate@uniwest.com \
--cc=ankitjain1580@yahoo.com \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).