Address-space randomization is a technique used to fortify systems against buffer overflow attacks. The idea is to introduce artificial diversity by randomizing the memory location of certain system components. This mechanism is available for both Linux (via PaX ASLR) and OpenBSD. We study

single address space for persistent data coexists with private segments for temporary data. In conclusion, this proposal is compared to previous systems.

Our first attempts at virtualizing memory will be very simple, almost laughably so. Go ahead, laugh all you want; pretty soon it will be the OS laughing at you, when things get quite a bit more complex. Specifically, we will assume for now that the user’s address space must be placed contiguously

Our first attempts at virtualizing memory will be very simple, almost laughably so. Go ahead, laugh all you want; pretty soon it will be the OS laughing at you, when things get quite a bit more complex. Specifically, we will assume for now that the user’s address space must be placed contiguously

-sharing operating system, address spaces can be used to encapsulate the time-sharing subsystem. However, in practice designers seldomly use address spaces for this purpose, fearing that extra cost induced thereby limits the system's predictability. To analyze this cost, we compared in detail two systems

This paper presents an analysis of the performance potential and limitation of the so-called small-space scheme, where several logical address spaces are securely multiplexed onto a single hardware address space. This can be achieved on the IA-32 architecture by using the segment registers

Persistence has long been difficult to integrate into operating systems. The main problem is that pointers lose their meaning once they are taken out of their address-space. We present a distributed system which has a single address-space encompassing all virtual memory of every node in the system

Recent microprocessor announcements show a trend toward wide-address computers: architectures that support 64 bits of virtual address space. Such architectures facilitate fundamentally new operating system organizations that promote efficient data sharing and cooperation, both between complex

library, really) that sat inmemory (start-ing at physical address 0 in this example), and there would be one run-ning program (a process) that currently sat in physical memory (starting at physical address 64k in this example) and used the rest of memory. There were few illusions here, and the user didn

(a library, really) that sat in memory (starting at physical address 0 in this example), and there would be one running program (a process) that currently sat in physical mem-ory (starting at physical address 64k in this example) and used the rest of memory. There were few illusions here