ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Sort of. You are running in a system that gives out cpu time in slices (quanta). If some process that has nothing to do with what you are doing needs time, it will get it.
You need to develop some kind of inter-thread communication scheme using sempahores or whatever is appropriate. Just guessing that streamtime will be 13000 ms and then sleeping that long will get you in trouble. You need to have each transmission thread signal <I am Done>
and then have one controlling thread wait until it gets all three of these signals or semaphores or whatever, before it tries to send the next batch of data.
You can get relatively close, but most of the time you'll find people implement protocols for what data should look like (start sequence, stop sequence, check sum) rather then timing schemes for how data should come because they are safer. Technically speaking, if the kernel decides it needs to do something more important it could cut you off in the middle of your routine. You could check out the RTLinux extensions and implement a kernel module for the timing that would easily get you the resolution you want.
One of the timing issues I imagine you'll run into is the fact that it is very hard to syncronize the clock on two different machines across the network, especially for us resolutions. And if you get off sync you'll end up with a huge mess.