Re: [patch] SLQB v2

[Christoph Lameter]

On Fri, 2 May 2008, Nick Piggin wrote:

> But overloading struct page values happens in other places too. Putting
> everything into struct page is not scalable. We could also make kmalloc

Well lets at least attempt to catch the biggest users. Also makes code 
clearer if you f.e. use page->first_page instead of page->private for 
compound pages.

kmalloc is intended to return an arbitrary type. struct page has a defined 
format that needs to be respected.

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