2 citations found. Retrieving documents...
Marshall Kirk McKusick and Michael J. Karels. Design of a general-purpose memory 75 allocator for the 4.3bsd UNIX kernel. In Proceedings of the Summer 1988 USENIX Conference, San Francisco, California, June 1988. USENIX Association.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Dynamic Storage Allocation: A Survey and Critical Review - Wilson, Johnstone, Neely.. (1995)   (104 citations)  (Correct)

....we believe are important. To our knowledge, this is by far the most thorough review to date, but it should not be considered detailed or exhaustive; valuable points or papers may have escaped our notice. 95 We have left out work on concurrent and parallel allocators (e.g. GW82, Sto82, BAO85, MK88, EO88, For88, Joh91, JS92, JS92, MS93, Iye93] which are beyond the scope of this paper. We have also neglected mainly analytical work (e.g. Kro73, Bet73, Ree79, Ree80, McI82, Ree82, BCW85] to some degree, be 94 This is not quite necessarily true. For applications that do little freeing, ....

Marshall Kirk McKusick and Michael J. Karels. Design of a general-purpose memory 75 allocator for the 4.3bsd UNIX kernel. In Proceedings of the Summer 1988 USENIX Conference, San Francisco, California, June 1988. USENIX Association.


The Slab Allocator: An Object-Caching Kernel Memory Allocator - Bonwick (1994)   (18 citations)  (Correct)

....the first dozen fields of an inode (48 bytes) are frequently referenced. Then the majority of inode related memory traffic will be Such allocators are common because they are easy to implement. For example, 4. 4BSD and SVr4 both employ power of two methods [McKusick88, Lee89]. at addresses between 0 and 47 modulo 512. Thus the cache lines near 512 byte boundaries will be heavily loaded while the rest lie fallow. In effect only 9 (48 512) of the cache will be usable by inodes. Fully associative caches would not suffer this problem, but current hardware trends are ....

.... resides on a single page. Thus a single TLB entry covers most of the action. 5. Performance This section compares the performance of the slab allocator to three other well known kernel memory allocators: SunOS 4.1.3, based on [Stephenson83] a sequential fit method; 4. 4BSD, based on [McKusick88], a power oftwo segregated storage method; SVr4, based on [Lee89] a power of two buddy system method. This allocator was employed in all previous SunOS 5.x releases. To get a fair comparison, each of these allocators was ported into the same SunOS 5.4 base system. This ensures that we are ....

Marshall Kirk McKusick and Michael J. Karels, Design of a General Purpose Memory Allocator for the 4.3BSD UNIX Kernel. Proceedings of the Summer 1988 Usenix Conference, pp. 295-303.

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