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: Fri, 17 Mar 2006 14:09:04 +0000 [thread overview]
Message-ID: <441AC300.8020003@yahoo.com.au> (raw)
In-Reply-To: <yq07j6tuq05.fsf@jaguar.mkp.net>
Jes Sorensen wrote:
>>>>>>"Nick" = Nick Piggin <nickpiggin@yahoo.com.au> writes:
>
>
> Nick> Jes Sorensen wrote:
>
>>>+ vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED | VM_PFNMAP);
>
>
> Nick> VM_PFNMAP actually has a fairly specific meaning [unlike the
> Nick> rest of them :)] so you should be careful with it. Actually if
> Nick> you set vm_pgoff in the right way, then that should enable you
> Nick> to do COWs on these areas if that is what you want.
>
> Yup, I went through that when I started using it. I think you guided
> me through it :-)
>
> 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 ;)]
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
WARNING: multiple messages have this Message-ID (diff)
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 01:09:04 +1100 [thread overview]
Message-ID: <441AC300.8020003@yahoo.com.au> (raw)
In-Reply-To: <yq07j6tuq05.fsf@jaguar.mkp.net>
Jes Sorensen wrote:
>>>>>>"Nick" == Nick Piggin <nickpiggin@yahoo.com.au> writes:
>
>
> Nick> Jes Sorensen wrote:
>
>>>+ vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED | VM_PFNMAP);
>
>
> Nick> VM_PFNMAP actually has a fairly specific meaning [unlike the
> Nick> rest of them :)] so you should be careful with it. Actually if
> Nick> you set vm_pgoff in the right way, then that should enable you
> Nick> to do COWs on these areas if that is what you want.
>
> Yup, I went through that when I started using it. I think you guided
> me through it :-)
>
> 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 ;)]
--
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 14:09 UTC|newest]
Thread overview: 42+ 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-16 16:55 ` Jes Sorensen
2006-03-17 0:37 ` Andrew Morton
2006-03-17 0:37 ` Andrew Morton
2006-03-17 1:04 ` Linus Torvalds
2006-03-17 1:04 ` Linus Torvalds
2006-03-17 2:13 ` Robin Holt
2006-03-17 2:13 ` Robin Holt
2006-03-17 4:58 ` Benjamin Herrenschmidt
2006-03-17 4:58 ` Benjamin Herrenschmidt
2006-03-17 9:15 ` Jes Sorensen
2006-03-17 9:15 ` Jes Sorensen
2006-03-17 13:29 ` Carsten Otte
2006-03-17 13:29 ` Carsten Otte
2006-03-17 18:03 ` Christoph Hellwig
2006-03-17 18:03 ` Christoph Hellwig
2006-03-17 9:42 ` Jes Sorensen
2006-03-17 9:42 ` Jes Sorensen
2006-03-17 12:29 ` Carsten Otte
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:28 ` Jes Sorensen
2006-03-17 12:38 ` [patch 2/2] mspec driver " Jes Sorensen
2006-03-17 12:38 ` Jes Sorensen
2006-03-17 13:36 ` [patch 2/2] mspec driver Nick Piggin
2006-03-17 13:36 ` Nick Piggin
2006-03-17 14:04 ` Jes Sorensen
2006-03-17 14:04 ` Jes Sorensen
2006-03-17 14:09 ` Nick Piggin [this message]
2006-03-17 14:09 ` Nick Piggin
2006-03-17 14:11 ` Jes Sorensen
2006-03-17 14:11 ` Jes Sorensen
2006-03-17 14:16 ` Nick Piggin
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:51 ` Carsten Otte
2006-03-17 13:53 ` Carsten Otte
2006-03-17 13:53 ` Carsten Otte
2006-03-17 13:56 ` Nick Piggin
2006-03-17 13:56 ` Nick Piggin
2006-03-17 13:58 ` Jes Sorensen
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=441AC300.8020003@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 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.