From: Christoph Hellwig <hch@lst.de>
To: carsteno@de.ibm.com
Cc: Jes Sorensen <jes@sgi.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
hch@lst.de, Hugh Dickins <hugh@veritas.com>
Subject: Re: [patch] mspec - special memory driver and do_no_pfn handler
Date: Fri, 17 Mar 2006 19:03:55 +0100 [thread overview]
Message-ID: <20060317180355.GA8232@lst.de> (raw)
In-Reply-To: <441AB9A9.2000704@de.ibm.com>
On Fri, Mar 17, 2006 at 02:29:13PM +0100, Carsten Otte wrote:
> Jes Sorensen wrote:
> > Well then the question is, would it simplify the code using no_pfn in
> > this case? Hacking up fake struct page entries seems even more of a
> > hack to me.
> I second that. That's were we are with our dcss xip thing today.
> It _is_ a hack to have a struct page that you don't need.
The same is true for the SPU support. The way it's done currently works
which is great, but the way it's done is everything but nice.
next prev parent reply other threads:[~2006-03-17 18:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 16:55 [patch] mspec - special memory driver and do_no_pfn handler Jes Sorensen
2006-03-17 0:37 ` Andrew Morton
2006-03-17 1:04 ` Linus Torvalds
2006-03-17 2:13 ` Robin Holt
2006-03-17 4:58 ` Benjamin Herrenschmidt
2006-03-17 9:15 ` Jes Sorensen
2006-03-17 13:29 ` Carsten Otte
2006-03-17 18:03 ` Christoph Hellwig [this message]
2006-03-17 9:42 ` Jes Sorensen
2006-03-17 12:29 ` Carsten Otte
2006-03-17 12:28 ` [patch 1/2] do_no_pfn handler (was: Re: [patch] mspec - special memory driver and do_no_pfn handler) Jes Sorensen
2006-03-17 12:38 ` [patch 2/2] mspec driver " Jes Sorensen
2006-03-17 13:36 ` [patch 2/2] mspec driver Nick Piggin
2006-03-17 14:04 ` Jes Sorensen
2006-03-17 14:09 ` Nick Piggin
2006-03-17 14:11 ` Jes Sorensen
2006-03-17 14:16 ` Nick Piggin
2006-03-17 13:51 ` [patch] mspec - special memory driver and do_no_pfn handler Carsten Otte
2006-03-17 13:53 ` Carsten Otte
2006-03-17 13:56 ` Nick Piggin
2006-03-17 13:58 ` 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=20060317180355.GA8232@lst.de \
--to=hch@lst.de \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=carsteno@de.ibm.com \
--cc=hugh@veritas.com \
--cc=jes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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