Messages in this thread | | | Date | Thu, 1 May 2008 18:28:57 -0700 (PDT) | From | Christoph Lameter <> | Subject | Re: [patch] SLQB v2 |
| |
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.
| |