linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch 1/5] mm: remap_vmalloc_range
Date: Fri, 21 Apr 2006 09:43:45 +0200	[thread overview]
Message-ID: <20060421074345.GN21660@wotan.suse.de> (raw)
In-Reply-To: <20060421074156.GM21660@wotan.suse.de>

On Fri, Apr 21, 2006 at 09:41:57AM +0200, Nick Piggin wrote:
> On Fri, Apr 21, 2006 at 12:29:38AM -0700, Andrew Morton wrote:
> > 
> > When replacing calls to remap_pfn_rage() with calls to remap_valloc_range():
> > 
> > - remap_pfn_range() sets VM_IO|VM_RESERVED|VM_PFNMAP on the user's vma. 
> >   remap_valloc_range() sets only VM_RESERVED.
> 
> Yep, it doesn't use PFNMAPs (we can always user the underlying struct
>  page), nor is it IO space. The only change that should be seen, as
> noted in patch 4/5, is that get_user_pages will work on all mappings
> now. I don't think there is a downside to this?

By "change that should be seen", I mean the only change that
userspace should see.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-04-21  7:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21  6:43 [patch 0/5] mm: improve remapping of vmalloc regions Nick Piggin
2006-04-21  6:43 ` [patch 1/5] mm: remap_vmalloc_range Nick Piggin
2006-04-21  7:17   ` Andrew Morton
2006-04-21  7:33     ` Nick Piggin
2006-04-21  7:59       ` Andrew Morton
2006-04-21  8:06         ` Nick Piggin
2006-04-21  7:29   ` Andrew Morton
2006-04-21  7:41     ` Nick Piggin
2006-04-21  7:43       ` Nick Piggin [this message]
2006-04-21  8:02       ` Andrew Morton
2006-04-21  6:43 ` [patch 2/5] mm: remove vmalloc_to_pfn Nick Piggin
2006-04-21  6:55   ` Nick Piggin
2006-04-21  6:43 ` [patch 3/5] mm: remove rvmalloc Nick Piggin
2006-04-21  6:43 ` [patch 4/5] mm: extra remap_vmalloc_range check Nick Piggin
2006-04-21  6:44 ` [patch 5/5] drivers: leave vm_flags alone Nick Piggin
  -- strict thread matches above, loose matches on Subject: below --
2006-04-20 17:06 [patch 0/5] mm: improve remapping of vmalloc regions Nick Piggin
2006-04-20 17:06 ` [patch 1/5] mm: remap_vmalloc_range Nick Piggin
2006-04-20 17:22   ` Christoph Hellwig
2006-04-20 17:33     ` Nick Piggin
2006-04-20 18:09   ` Nick Piggin

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=20060421074345.GN21660@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).