![]() | ||||||||||
Messages in this thread |
On Wed, Dec 04, 2002 at 08:32:58PM -0800, Andrew Morton wrote: > Where in the kernel is such a large number of 4-, 8- or 16-byte > objects being used? > The slab allocator will support caches right down to 1024 x 4-byte > objects per page. Why is that not appropriate? > If it is for locality-of-reference between individual objects then > where in the kernel is this required, and are performance measurements > available? It is very unusual to have objects which are so small, > and a better design would be to obtain the locality of reference > by aggregating the data into an array or structure. I will argue not on the frequency of calls but on the preciousness of space; highmem feels very serious pain when internal fragmentation of pinned pages occurs (which this is designed to prevent). I don't have direct experience with this patch/API, but I can say that fragmentation in ZONE_NORMAL is deadly (witness pagetable occupancy vs. ZONE_NORMAL consumption, which motivated highpte, despite my pagetable reclamation smoke blowing). Bill - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-03-22 12:31 [from the cache] ©2003-2008 | ||||||||||