RTOS and GPOS

-
The difference between an RTOS and a general purpose OS is really a matter of emphasis. If you asked the designer of a general purpose OS "what is the worst case latency in your OS", they would probably answer "I don't know". It isn't something that they generally worry about unless it gets so long that someone important enough complains about it. If you ask an RTOS designer the same question, they can give you a definite answer.

also if you consider the memory used... then the RTOS will consume little memory & our general purpose OSs.. you know that... as the new OS release are coming out... they are occupying more memory...
yeah as you said RTOS are used in Embedded Systems... The main aim in our embedded system is that... the responce should be quick... because.. these system are used in very critical situations/applications... like in our modern cars...If these cars encounter in an accident then immidiately in a fraction the airbags will be blown... to protect the driver... but if you use the general OS.. then.. --- help them... So If you use winXP in a camera processors with P4 3.5GH then... its okie having a latest & high speed processor... still the responce time of the OS will be the same.. in winXP.... here we just need to capture a pic in fraction of second.

there is no problem if you use different configuration for your camera... then you have to wait to capture your pic... click it & then wait forfew seconds to get the picture....
So... i think you got the Importance of RTOS over OS

Real Time OS:
1. It is time deterministic
2. High accuracy Resource allocation
3. Configurable Kernel
4. BSP support for external dependancy to another system
5. Mostly used in Embedded systems

Normal OS:
1. It may or may not be time deterministic ( Eg Hard OS is time - deterministic)
2. General level Resource allocation
3. Configurable(may or may not be) Kernel(e.g. in LINUX you can configure some application level kernel)
4. Package support is available here
5. Mostly used in general purpose systems


Reference:www.edaboard.com

Comments

Post a Comment

Popular posts from this blog

Airtel Digital tv remote factory reset and reprogram

-
Following is the way to reset Airtel Digial tv universal remote reset procedure. 1. Press red button and ok button together untill red light blinks twice. 2. Release the buttons and press 980 buttons one by one (not together)   3. Red light will blink again two times, now press ok button. Reprogramming There are 5 basic functions which your new Airtel remote needs to learn about your TV 1. TV Power code 2. TV Mute code 3. AV code 4. TV VOL + code 5. TV VOL – code Steps for Universal remote setup: Step 1:  Bring Airtel digital TV remote in learning mode. Press and hold ‘’OK + Numeric 2” key for 3 seconds. The LED blinks twice to indicate that your Airtel remote is ready to learn. Step 2 :  Hold the source remote and Airtel remote in front of each other ( 3cm-6m apart). Step 3:  Press & release the key (First on Airtel remote and then on Source remote) which needs to be programmed in Airtel remote. Example: Press and release the TV Power key on both remotes and release. The A
Read more

Tracking Linux kworker threads

-
How to find out which part of kernel/module has created this workqueue. How to track a kworker-thread named for example ''kworker/0:3 to its origin in kernel-space? I found  this thread on lkml  that answers your question a little. (It seems even Linus himself was puzzled as to how to find out the origin of those threads.) Basically, there are two ways of doing this: $ echo workqueue:workqueue_queue_work > /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace_pipe > out.txt (wait a few secs) For this you will need  ftrace  to be compiled in your kernel, and to enable it with: mount -t debugfs nodev /sys/kernel/debug More information on the function tracer facilities of Linux is available in the  ftrace.txt documentation . This will output what threads are all doing, and is useful for tracing multiple small jobs. cat /proc/THE_OFFENDING_KWORKER/stack This will output the stack of a single thread doing a lot of work. It may allow you
Read more

Asynchronus I/O (AIO) in vxworks and Linux

-
In generic Asynchronus I/O (AIO) can be designed using User lavel or in Kernel level. In user level 1) Process needs async callback/notification create another thread and process which goes to sleep on blocking calls (read/write/ioctls/select) 2) One Async master handler (process/thread) keeps track.All the process needs the service submit job to them.The master handler handles the async fd in Blocking mode and reply to requesting processes (or call the callback function) using some async notificatin like signal. In Kernel Level 1) Call some system call and submit some job to kernel workQ .After work is complete kernel notify using signal to user space.   In VxWorks :  aioPxLib provide the POSIX 1003.1b standard.Which is task implementation of aio service. functions available: 1) aio_read() - initiate an asyn. read. 2) aio_write() - initiate an syn write 3) aio_listio() - Initiate a aio list upto LIO_MAX 4) aio_error() - Get an aio error status. 5) aio_return() - Get a
Read more