Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Real time on a PC with a CPU is referring to clock time of the CPU, to call and execute a function call in real time is -- "right now" without delay, this is machine language that manipulates the hardware of the system, whereas software has a delay to it due to having to go through the API or a driver therefore, not actually speaking to the hardware directly. Hence a delay in time occurs due to this effect of having to go through a proxy of sorts first before the hardware actually receives the call to do something. It is not real time programming but that other one which the name of it escapes me at this moment.
In computer science, real-time computing, or reactive computing describes hardware and software systems subject to a "real-time constraint", for example from event to system response. Real-time programs must guarantee response within specified time constraints, often referred to as "deadlines". Real-time responses are often understood to be in the order of milliseconds, and sometimes microseconds. A system not specified as operating in real time cannot usually guarantee a response within any timeframe, although actual or expected response times may be given.
therefore anything other programming will be slower then "real time" if it is not machine code assembly language.
Actually, the most likely explanation in this case is that your times are just too small to measure (meaningfully). When you're dealing in the realm of "0.00x seconds," 'irrelevant curiosities' (ahem...) may appear.