All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: Robin Holt <holt@sgi.com>
Cc: Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	Hugh Dickins <hugh@veritas.com>, Carsten Otte <cotte@de.ibm.com>,
	bjorn_helgaas@hp.com
Subject: Re: [patch] do_no_pfn
Date: Tue, 20 Jun 2006 10:01:10 +0200	[thread overview]
Message-ID: <4497AB46.4000402@sgi.com> (raw)
In-Reply-To: <20060619224952.GA17685@lnx-holt.americas.sgi.com>

Robin Holt wrote:
> On Mon, Jun 19, 2006 at 03:06:05PM +0200, Andi Kleen wrote:
>> The big question is - why do you have pages without struct page? 
>> It seems ... wrong.
[snip]
> Are you saying the for the mspec pages we should extend the vmem_map,
> partially populate the regions for the mspec pages, mark those pages as
> uncached and reserved and then turn them over to the uncached allocator?
> Seems like we have done a lot of extra work to put a struct page behind
> a page which requires special handling.

Note that Bjorn Helgas has a case where he needs this as well.

We could fake the pages by giving them a struct page, but it really
makes no point as you say.

Cheers,
Jes

  reply	other threads:[~2006-06-20  8:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19  9:19 [patch] do_no_pfn Jes Sorensen
2006-06-19 13:06 ` Andi Kleen
2006-06-19 22:49   ` Robin Holt
2006-06-20  8:01     ` Jes Sorensen [this message]
2006-06-20  8:13       ` Andi Kleen
2006-06-20  8:40         ` Jes Sorensen
2006-06-20  8:48           ` Andi Kleen
2006-06-20  9:12             ` Jes Sorensen
2006-06-20  9:35               ` Andi Kleen
2006-06-20 11:02                 ` Robin Holt
2006-06-21  9:50                 ` Jes Sorensen
2006-06-20 16:03       ` Bjorn Helgaas
2006-06-21  7:38         ` Carsten Otte
2006-06-20  8:58     ` Carsten Otte
2006-06-27 12:46 ` [patch] do_no_pfn - against latest git Jes Sorensen

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=4497AB46.4000402@sgi.com \
    --to=jes@sgi.com \
    --cc=ak@suse.de \
    --cc=bjorn_helgaas@hp.com \
    --cc=cotte@de.ibm.com \
    --cc=holt@sgi.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.