User Level IPC and Device Management in the Raven Kernel (1993) [11 citations — 0 self]
Abstract:
The increasing bandwidth of networks and storage devices in recent years has placed greater emphasis on the performance of low level operating system services. Data must be delivered between hardware devices and user applications in an efficient matter. Motivated by the need for low overhead operating system services, the Raven kernel utilizes user level implementation techniques to reduce kernel intervention for many common services. In particular, our user level send/receive/reply communication implementation generates no kernel interactions per iteration in the best case, and two kernel interactions in the worst case. In more general cases, we observe approximately one kernel interaction for every two send/receive/reply iterations. Device driver support is also done entirely at the user level reducing copy costs and context switching. 1 Introduction The speed of network channels and storage devices has increased by an order of magnitude in recent years (10Mbps Ethernet to 100Mbps F...
Citations
| 256 | The V Distributed System – Cheriton - 1988 |
| 240 | A new kernel foundation for unix development – Mach - 1986 |
| 177 | The structuring of systems using upcalls – Clark - 1985 |
| 119 | Scheduling and IPC Mechanisms for Continuous Media – Govindan, Anderson - 1991 |
| 114 | An Architectural Overview of QNX – Hildebrand - 1992 |
| 104 | Using Continuations to Implement Thread Management and Communication in Operating Systems – Draves, Bershad, et al. - 1991 |
| 53 | User-level interprocess communication for shared memory multiprocessors – Bershad, Anderson, et al. - 1991 |
| 11 | Optimizing memorybased messaging for scalable shared memory multiprocessor architectures – Cheriton, Kutter - 1993 |

