From: Jes Sorensen <jes@sgi.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andrew Morton <akpm@osdl.org>,
torvalds@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 2/2] mspec driver
Date: Fri, 17 Mar 2006 15:11:48 +0100 [thread overview]
Message-ID: <441AC3A4.801@sgi.com> (raw)
In-Reply-To: <441AC300.8020003@yahoo.com.au>
Nick Piggin wrote:
> Jes Sorensen wrote:
>> We don't want COW here as the access is backed by special behavior in
>> the memory controller. We only allow shared mappings for that reason.
>>
> No problem, I think you should just stop using the VM_PFNMAP flag then.
> [Linus should jump in here if I'm wrong ;)]
I'd have to go back and find the discussion to verify, but if I
remember correctly the conclusion was that I needed to use it in
order to make sure that vm_normal_page() didn't start thinking it was
in fact a real page, ie. VM_PFNMAP + never a COW mapping..
Chers,
Jes
next prev parent reply other threads:[~2006-03-17 14:12 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
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 [this message]
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=441AC3A4.801@sgi.com \
--to=jes@sgi.com \
--cc=akpm@osdl.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=nickpiggin@yahoo.com.au \
--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