Hello, > ... > > 2) Why are there general caches up to a size of 128K byte? Since a slab > > consists of physically contiguous pages, one might call right into the > > buddy system to get chunks of memory that are a multiple of a page size. > > What is the benefit of allocating memory chunks that are a multiple of > > a page size by using kmalloc()/kmem_cache_alloc() rather than > > get_free_pages? > > Memory fragmentation. By grouping objects of the same type and similar > lifetimes, slab helps prevent the pinning of many individual pages across > the system. Since slab allocations cannot be relocated, this helps when > other allocations need to obtain non-0 order pages. Thank you for your reply. Could you detail how memory fragmentation is reduced? I understand the assumption that objects of the same type (and therefore same size) tend to have similar lifetimes. However the general caches for objects that are a multiple of a page size contain one object per cache (see /proc/slabinfo). Each time such an object is allocated by kmalloc(), the slab allocator will therefore use a new slab (which is allocated by calling into the buddy system). So what is the difference with respect to memory fragmentation compared to calling straight the buddy system by using get_free_pages()? regards Martin -- Supercomputing System AG email: maletinsky@scs.ch Martin Maletinsky phone: +41 (0)1 445 16 05 Technoparkstrasse 1 fax: +41 (0)1 445 16 10 CH-8005 Zurich -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
