linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Nick Piggin <npiggin@suse.de>
Cc: "Ahmed S. Darwish" <darwish.07@gmail.com>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] SLQB v2
Date: Thu, 1 May 2008 18:28:57 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0805011825420.13697@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20080502012321.GE30768@wotan.suse.de>

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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-05-02  1:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10 19:31 [patch] SLQB v2 Nick Piggin
2008-04-15  3:44 ` Ahmed S. Darwish
2008-05-01  1:54   ` Nick Piggin
2008-05-01 19:29     ` Christoph Lameter
2008-05-02  0:43       ` Nick Piggin
2008-05-02  1:14         ` Christoph Lameter
2008-05-02  1:23           ` Nick Piggin
2008-05-02  1:28             ` Christoph Lameter [this message]
2008-05-02  1:48               ` Nick Piggin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0805011825420.13697@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=darwish.07@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).