From: Jes Sorensen <jes@sgi.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
hch@lst.de, cotte@de.ibm.com, Hugh Dickins <hugh@veritas.com>
Subject: Re: [patch] mspec - special memory driver and do_no_pfn handler
Date: Fri, 17 Mar 2006 10:15:32 +0100 [thread overview]
Message-ID: <441A7E34.90508@sgi.com> (raw)
In-Reply-To: <1142571490.9022.37.camel@localhost.localdomain>
Benjamin Herrenschmidt wrote:
>> Quite frankly, I don't think nopfn() is a good interface. It's only usable
>> for one single thing, so trying to claim that it's a generic VM op is
>> really not valid. If (and that's a big if) we need this interface, we
>> should just do it inside mm/memory.c instead of playing games as if it was
>> generic.
>
> Or just use sparsemem and create struct pages for your hw :) we do that
> for SPUs on Cell, works like a charm.
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.
Cheers,
Jes
next prev parent reply other threads:[~2006-03-17 9:15 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 [this message]
2006-03-17 13:29 ` Carsten Otte
2006-03-17 18:03 ` Christoph Hellwig
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=441A7E34.90508@sgi.com \
--to=jes@sgi.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=cotte@de.ibm.com \
--cc=hch@lst.de \
--cc=hugh@veritas.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