From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jes Sorensen <jes@sgi.com>
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: Sat, 18 Mar 2006 00:36:40 +1100 [thread overview]
Message-ID: <441ABB68.1020502@yahoo.com.au> (raw)
In-Reply-To: <yq0bqw5utyc.fsf_-_@jaguar.mkp.net>
Jes Sorensen wrote:
> +static int
> +mspec_mmap(struct file *file, struct vm_area_struct *vma, int type)
...
> + vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED | VM_PFNMAP);
VM_PFNMAP actually has a fairly specific meaning [unlike the rest of
them :)] so you should be careful with it. Actually if you set vm_pgoff
in the right way, then that should enable you to do COWs on these areas
if that is what you want.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-03-17 13:36 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 ` Nick Piggin [this message]
2006-03-17 14:04 ` [patch 2/2] mspec driver 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=441ABB68.1020502@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=cotte@de.ibm.com \
--cc=hch@lst.de \
--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