linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Nick Piggin <npiggin@suse.de>,
	Arjan van de Ven <arjan@infradead.org>,
	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: Mon, 23 Jan 2006 10:20:03 +0100	[thread overview]
Message-ID: <20060123092002.GA26399@wotan.suse.de> (raw)
In-Reply-To: <20060123084715.GA9241@osiris.boeblingen.de.ibm.com>

On Mon, Jan 23, 2006 at 09:47:15AM +0100, Heiko Carstens wrote:
> > > > 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..
> > 
> > I guess it doesn't seem like something drivers would need to use
> > (and none appear to do anything like it).
> 
> And I thought this could/should be used together with vm_insert_page() that
> drivers are supposed to use nowadays instead of remap_pfn_range().
> Why shouldn't drivers use this?
> 

Actually fs/ramfs/file-nommu.c does use this (but it need not because
!CONFIG_MMU page allocator already does something similar).

But largely, no in-tree drivers use the facility so I think it would
be good for the mm folk to consider the first use case if and when it
comes up. So I've added a comment in split_page to that effect.

Thanks,
Nick


      parent reply	other threads:[~2006-01-23  9:20 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
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 [this message]

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=20060123092002.GA26399@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=arjan@infradead.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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).