ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It totally depends on how strict your real time requirement is. If you're writing a hard real time app, an ordinary Linux kernel may not be a good choice. If you're writing a soft real time app, it could work quite well. In the end you just have to try it and see. This looks quite informative: http://www.metrowerks.com/pdf/Metrow...as_RTOS_v2.pdf
I took a closer look at your timing schemes and since .5 second is the tightest you need you can probably handle the just fine. In fact, if you are using a linux kernel with the enhanced real time clock you could set the frequency of that and use it for timing. I am not sure exactly how that works but mplayer uses that for video timing so you can probably look at there code.
What kind of server is this? As I said before, only use timing to define a network protocol if there is absolutely no other way.
oh duh... I don't know where I get .5 seconds from.
I am not sure what the resolution of the rtc is, but 555 usecs is pretty tight timing you could easily miss if the kernel decides it needs to do something else. If I personally had to have timing like that I would write an RTLinux kernel module. But that doesn't mean that you could possibly do it another way.
Is there something external that is dictating that timing?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.