If you were writing code for a real time operating system, what restriction migh

Question

If you were writing code for a real time operating system, what restriction might you want to impose on the system? Hint: Think about the type of things that cause unpredictable reaction times. (How might a memory access be delayed, for example?)

Why should assembly language be avoided for general application development? Under what ciscumstances is assembly language preferred ir required?

In what way are n-tiered transaction processing architectures superior to single tier architectures? Which usually cost more?

Explanation / Answer

1. Related to OS

Here, I have dealt with errors which can happen due to both system and manual. Also, while designing the operating system, what all things should be used and what all things should be taken care of.

Here you go.

There is a certain amount of folklore about what is good and what is bad floating around in the operating systems community, but surprisingly little has been written down.

Operating system design is more of an engineering project than an exact science. It is much harder to set clear goals and to meet them.

8 issues that make designing an operating system much hard.

First, operating systems have become extremely large programs. No one person can sit down at a PC and dash off a serious operating system in a few months.

All current versions of UNIX exceed 3 million lines of code; Windows Vista and Windows 7 have over 5 million lines of kernel code (and over 50 million lines of total code). No

one person can understand 3

Related Questions

Navigate

• Browse (All)
• Browse I
• Subjects