M. Pietrek, Windows Internals, Addison Wesley, Reading, MA, 1993.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....this can be deduced from the current status of all processes. Thus, whenever any process is running or ready to run, the processor should not be turned off; when all processes are blocked, the processor should be turned off [34 36] Examples of operating systems using this strategy are Windows [37, 38] and UNIX. MacOS, however, uses a different strategy, perhaps because its strategy was designed when processors did suffer side effects from turning off. It uses an inactivity threshold, as is commonly used for hard disk power management. The processor is shut off when there have been no disk ....

M. Pietrek, Windows Internals, Addison Wesley, Reading, MA, 1993.

....own thread scheduling. While this assumption holds mostly true under UNIX operating systems where multi programming capability was built into the system from day one, it does not always hold true in Microsoft Windows software, a system initially developed with no multi programming capability [22][28]. We expect such programs to slowly disappear as newer versions of Microsoft Windows support kernel level threads 14 and various coding guidelines encourage use of such facilities [10] 30] We have also decided to treat network related delays as a black box. Consider a client server architecture ....

Matt Pietrek, Windows Internals, Addison-Wesley, 1993.

....packet loss and limited throughput when comparing to Microsoft TCP IP 32, which use Virtual Device Drivers (VxD) mechanisms. We have not tested the VxD version of PC TCP but there should be performance gain. This observation is consistent with the way network I Os are performed in Windows [23,24], which implies that VxD implementation always performs much better than TSR. Our current implementation of BDL, MRDP, and VTP all run in the System VM within Windows, which supports only non preemptive multitasking. The current BDL implementation is based on Windows Socket (WinSock) 25] ....

M. Pietrek. Windows Internals. Addison-Wesley, Reading Mass, 1993.

....code for Windows, we did have a Windows debugger that made it possible to single step through interrupt handlers and other parts of the system, 1 helping us answer questions about Windows control structure. There are many books which provide a more comprehensive technical description of Windows [6, 29, 35, 38] 2.2 Windows NT Unlike Windows, Windows NT supports protected address spaces, preemptive multi tasking and multiple APIs, including the Win32 API [41] as well as the MS DOS and Windows APIs. Windows NT implements system APIs using user level server processes called protected subsystems. As such, ....

. Matt Pietrek. Windows Internals. Addison-Wesley, Reading Massachusetts, 1993.

....it possible to single step through interrupt handlers and other parts of the system. This made it possible to answer many questions about Windows control structure in spite of the lack of source code. In addition, an abundance of reference books on Windows exists. See [Chappell 94, Microsoft 90, Pietrek 93, Schulman et al. 92] for a more complete description of Windows internals. 2.2 Windows NT Windows NT is microkernel operating system that supports protected address spaces, preemptive multi tasking, and multiple application APIs, including the MS DOS and Win16 APIs supported by Windows as well ....

Matt Pietrek, Windows Internals, Addison-Wesley, Reading Massachusetts, 1993.

....can be deduced from the current status of all processes. Thus, whenever any process is running or ready to run, the processor should not be turned off; when all processes are blocked, the processor should be turned off [49, 72, 74] Examples of operating systems using this strategy are Windows [15, 62] and UNIX. MacOS, however, uses a different strategy, perhaps because its strategy was designed when processors did suffer side effects from turning off. It uses an inactivity threshold, as is commonly used for hard disk power management. The processor is shut off when there have been no disk ....

Pietrek, M. Windows Internals, Addison Wesley, Reading, MA, 1993.

.... it makes no attempt to police processes that make unfair processor time requests; in fact, one recognized problem with its power management is that if a single process requests events using PeekMessage rather than GetMessage or WaitMessage, then processor power management cannot take place [2, 11]. This problem is exactly the sort that the greediness technique was designed to alleviate, so we may find that, as we demonstrated for the MacOS, the effectiveness of the basic strategy is greatly improved by the use of such a technique. We would like to see the work described here continued in ....

M. Pietrek. Windows Internals, Addison Wesley, Reading, MA, 1993.

....any user can write new operating system code for an application, build it into a new kernel, install, and reboot. Of course, few users are actually capable of negotiating through system build procedures [ODE 91] let al..one writing new code for the system [Leffler et al. 89, Leffler McKusick 91, Pietrek 93] Moreover, security and integrity concerns generally make arbitrary user extensions unacceptable, either on a personal computer [Livingston 94] on a shared machine, or even a machine on a shared network. For example, in our shared computing environment, Macintosh users are not allowed to share ....

Pietrek, M. Windows Internals. Addison-Wesley Publishing, 1993.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC