Re: [RFC] Use compound pages for higher order slab allocations.

Christoph Lameter wrote:

+static inline struct page *virt_to_compound_page(const void *addr)
+{
+	struct page * page = virt_to_page(addr);
+
+	if (PageCompound(page))
+        	page = (struct page *)page_private(page);
+

This would end up in every kmem_cache_free/kfree call. Is it really worth the effort, are the high order allocation a problem? I'm against such a change without a clear proof that just using high order allocations is not possible.

--
   Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [RFC] Use compound pages for higher order slab allocations.
    • From: Christoph Lameter <[email protected]>

• References:
  • [RFC] Use compound pages for higher order slab allocations.
    • From: Christoph Lameter <[email protected]>

• Prev by Date: Re: Incorrect v4l patch in 2.6.15-rc4-git1
• Next by Date: Re: [spi-devel-general] Re: [PATCH 2.6-git] SPI core refresh
• Previous by thread: [RFC] Use compound pages for higher order slab allocations.
• Next by thread: Re: [RFC] Use compound pages for higher order slab allocations.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]