linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [rfc] split_page function to split higher order pages?
Date: Sat, 21 Jan 2006 15:17:04 +0100	[thread overview]
Message-ID: <1137853024.23974.0.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060121124053.GA911@wotan.suse.de>

On Sat, 2006-01-21 at 13:40 +0100, Nick Piggin wrote:
> Hi,
> 
> Just wondering what people think of the idea of using a helper
> function to split higher order pages instead of doing it manually?

Maybe it's worth documenting that this is for kernel (or even
architecture) internal use only and that drivers really shouldn't be
doing this..


  reply	other threads:[~2006-01-21 14:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21 12:40 [rfc] split_page function to split higher order pages? Nick Piggin
2006-01-21 14:17 ` Arjan van de Ven [this message]
2006-01-23  5:49   ` Nick Piggin
2006-01-23  8:47     ` Heiko Carstens
2006-01-23  8:54       ` Arjan van de Ven
2006-01-23  9:20       ` 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=1137853024.23974.0.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --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).