J. Itoh, Y. Yokote, and M. Tokoro. Scone: using concurrent objects for low-level operating system programming. In Proceedings of OOPSLA'95, pages 385--398, Austin, TX, USA, Oct. 1995.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....woven into the functional code by a so called aspect weaver at pre processing time. Although this approach clearly separates all aspects from the functional code (at design time) all aspects disappear at run time, what makes it very dicult (if not impossible) to adapt aspects dynamically. Apertos [5] introduces concurrent objects that separate mechanisms of synchronization, scheduling and interrupt mask handling from the functional code (such as a device driver) Therefore, programmers can concentrate on writing functional code without having to write auxiliary code for synchronization [4] ....

J. ichiro Itoh, Y. Yokote, and M. Tokoro. SCONE: Using Concurrent Objects for Low-level Operating System Programming. In Conference on Object-Oriented Programming Systems, Languages and Applications (OOPSLA), pages 385-398, 1995.

....tracking) deciding and acting. Observation variables capture the relevant aspects of the status of the system, and are provided by sensors. Sensor in this work also includes other awareness mechanisms such as monitoring by dedicated components in the middleware [3] 4] 8] in the operating system [10] and in the application managers. These techniques are necessary to capture system level measures such as throughput, CPU utilization, and average delay, and environment parameters such as subsystems used by a response, levels of competitive workloads. Failure detectors fall into the same group of ....

Jun-ichiro Itoh, Yasuhiko Yokoto, Mario Tokoro, "SCONE: Using Concurrent Objects for Low-level Operating System Programming". ACM OOPSLA'95

....application specific, such as message sizes, class or structure of data requests, relative importance of a request, and request contexts. Sensor in this work also includes other awareness mechanisms such as monitoring by dedicated components in the middleware[4] 6] 13] in the operating system [19] and in the application managers. These techniques are necessary to capture system level performance measures such as throughput, CPU utilization, and average delay, and environment parameters such as subsystems used by a response, levels of competitive workloads. Failure detectors fall into the ....

Jun-ichiro Itoh, Yasuhiko Yokoto, Mario Tokoro, "SCONE: Using Concurrent Objects for Low-level Operating System Programming". ACM OOPSLA'95

....services and to integrate the necessary support for it (such as a new communication protocol or a new disk caching strategy) even at runtime. Strict separation of functional and non functional code has proven to be an essential feature for adaptable, maintainable and reusable software [6][8] 11] In this paper we illustrate that the DiPS framework unifies component support, self adaptability and separation of concerns in one paradigm, which is a strong combination for system software. DiPS is not a complete operating system, but rather a component framework to build system ....

....model in the connectors, a well trained system engineer can apply the concurrency model independent from the software builder who developed the functional components. Separation of concurrency code from the functional code is an important feature in other paradigms such as concurrent objects in [6] and aspects in [8] Examples of DiPS connectors are the MutexConnector which only allows one thread at a time and the ActiveConnector which is composed of a buffer and a scheduler (see also the figure) 2.3 DiPS reflection points Scheduling or cache replacement policies will often depend on ....

J. Itoh, Y. Yokote and M. Tokoro. Scone: Using concurrent objects for low-level operating systems programming. Technical report, Department of Computer Science, Keio University, 1995.

....to be transparently added, removed or replaced (at run time) DiPS components are anonymously connected to each other. Strict separation of functional and non functional code (such as concurrency code) has proven to be an essential feature to become adaptable, maintainable and reusable software [3]. For example, popular websites handle more than 100 million page views a day which results in many thousands of concurrent i o requests. DiPS therefore allows fine grained per component concurrency control by its active connectors (AC) see figure) An AC encapsulates a scheduler thread (or a ....

J. Itoh, Y. Yokote, and M. Tokoro. Scone: Using concurrent objects for low-level operating system programming. Technical report, Department of Computer Science, Keio University, 1995.

....that behave optimally in all conditions. Scheduling or caching strategies are often specialized towards speci c situations and cannot adapt to unusual circumstances. Research in device driver development shows that device driver software needs support for concurrency control and adaptive behavior [IYT95] 2.1 Ad hoc network drivers Devices become more and more intelligent. An example of such an intelligent technology is Bluetooth [Gro99] Bluetooth devices are connected in an ad hoc fashion, i.e. not requiring prede nition and planning, as with a standard network. The exibility o ered by ....

....packet until a speci c event is received. Traditional systems, such as UNIX, o er the sleep and wakeup mechanism which is too complex and not modular. DiPS o ers a clear separation of functional code in the components and synchronization code in the connectors. A similar approach is de ned in [IYT95] When the device is recognized, a loader component locates the driver and actually loads it into memory. A specialized driver builder component nally instantiates the driver and connects it in the USB system structure. The builder approach is used at two di erent levels in the hub driver. On ....

J. Itoh, Y. Yokote, and M. Tokoro. Scone: Using concurrent objects for low-level operating system programming. Technical report, Department of Computer Science, Keio University, 1995.

....the safety and integrity of the system. Reflective operating systems [Yokote92] provide general high level mechanisms for modifying many aspects of system operation. While the general mechanisms in Apertos provide enormous power, they are also enormously difficult to implement efficiently [Itoh95]. This work differs from both extensible kernels and reflective operating systems in that it is a solution specialized for file systems. Other researchers are investigating global resource allocation strategies for improving overall file system performance [Cao95, Patterson95] The work in this ....

Itoh, J., Y. Yokote, and M. Tokoro. SCONE: Using Concurrent Objects for LowLevel Operating System Programming. Proceedings of OOPSLA '95, pages 385-398. 1995.

....that portray different points in the design space and that represent different operating system communities, page 10 of 15 such as the commercial sector, the main stream operating system research community, and the reflective community. The systems are summarized in Table 3. Apertos Apertos [10] is designed to support an open and mobile computing environment, as well as to introduce a new object oriented framework to combat complexity in large systems. Apertos consists solely of objects that operate in a heterogeneous environment. The system is composed of objects that contain ....

Itoh, J., Yokote, Y., Tokoro, M., "SCONE: Using Concurrent Objects for Low-level Operating System Programming," Proceedings of the ACM OOPSLA'95, October 1995.

....form an additional concern. This contrasts e.g. the shared memory multiprocessor architecture HFS is designed for. At the device driver side, another object oriented operating system, Apertos [30] has a very powerful reflective architecture to support reusable and easy towrite device drivers [15] and has the same goals of flexibility. However, they are not focusing on other aspects of distributed and parallel I O systems. The object oriented methodology has also been successfully applied to the device driver subsystem of the IBM AS 400 operating system in [2] 5. Conclusion The common ....

J. Itoh, Y. Yokote and M. Tokoro. "SCONE: Using Concurrent Objects for Low-level Operating System Programming" In Proceedings of Object-Oriented Programming Systems, Languages and Applications (OOPSLA). 1995.

No context found.

J. Itoh, Y. Yokote, and M. Tokoro. Scone: using concurrent objects for low-level operating system programming. In Proceedings of OOPSLA'95, pages 385--398, Austin, TX, USA, Oct. 1995.

No context found.

J. Itoh, Y. Yokote, and M. Tokoro. Scone: using concurrent objects for low-level operating system programming. In Proceedings of OOPSLA'95, pages 385--398, Austin, TX, USA, Oct. 1995.

No context found.

J. Itoh, Y. Yokote, and M. Tokoro. Scone: using concurrent objects for low-level operating system programming. In Proceedings of OOPSLA'95, pages 385--398, Austin, TX, USA, Oct. 1995.

No context found.

Jun ichiro Itoh, Yasuhiko Yokote, and Mario Tokoro. SCONE: Using Concurrent Objects for Low-level Operating System Programming. In Proceedings of Object-Oriented Programming Systems, Languages and Applications (OOPSLA) , pages 385-398, 1995.

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