Answer / mohsin

There are two major reson to consider before selecting any RTOS

1) Interuppt latency
2) Footprint (size of the executable which is generated
after compiling)
3) Context switching time is also considered as vital
element in selection

Answer / mujeer

Interrrupt Latency means the time taken by the processor to
pass the control to ISR after the interrupt is raised.
Certainly this is the hardware feature.

Footprint of the OS matters because with the same compiler
and same optimization techniques, Different OS's will have
different footprint.
So this is can be looked upon while selecting the RTOS.

RTOS can be chosen looking at various API support it
provides. Synchronization support, Scheduler algos, and
memory management of the OS.

Answer / endachata

(1) Interrupt latency means, the time taken by the processor
to service the interrupt. So, obviously the interrupt
latency depends on how good the Interrupt Service Routine
was written

(2) Foot print is completely related to compiler and its
optimization techniques

Answer / santosh

First thing i will look for open source RTOS, so that i can
modify it as per my application requirements. Further, it
will help in debugging software with confidence.


Context switching time is again in programmers hand(i.e.OS
porting work).

What is a Real-Time System ?

5 Answers  

---

What is the important aspect of a real-time system ?

6 Answers  

---

what is the need of creating 4GB of pages in linux?

1 Answers   TCS,

---

When would you choose bottom up methodology?

5 Answers   Knowx Innovations,

---

Describe different job scheduling in operating systems.

9 Answers  

---

What is the state of the processor, when a process is waiting for some event to occur?

14 Answers   MTS,

---

If two processes which shares same system memory and system clock in a distributed system, What is it called?

7 Answers  

---

I have been working on one thread which manage and control a couple of circular buffers. It has api for other thread to access. As the thread grows bigger and bigger, I split it as 3 to 4 threads which need to share common buffers, and also their api could be used by other threads, (not these three threads). Inside api, I also allow other threads to access these three threads' common buffers(more than one buffer). SO I have to use mutex to avoid race condition . But I found mutex will be everwhere in all the threads when they update the common buffer. I am wondering whether I could reduce mutex usage(more mutex will hure my system performance). any ideas for how to reduce mutex usage meanwhile to avoid race condition. Thanks

2 Answers  

---

What is priority inversion ? and What is the solution ?

6 Answers   Qualcomm, Tandberg, Wipro,

---

What do you mean by deadlock?

8 Answers   Bosch,

---

what is difference between IRQ and FRQ ?

4 Answers   Bosch,

---

Write a small dc shell script to find number of FF in the design

0 Answers  

---