From: Kyle McMartin <kyle@mcmartin.ca>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-arch@vger.kernel.org
Subject: Re: [patch] mm: rewrite vmap layer
Date: Tue, 19 Aug 2008 23:32:50 -0400 [thread overview]
Message-ID: <20080820033249.GA19241@phobos.i.cabal.ca> (raw)
In-Reply-To: <20080819103952.GE16446@wotan.suse.de>
On Tue, Aug 19, 2008 at 12:39:52PM +0200, Nick Piggin wrote:
> > Second question - will ARMs separate module area still work with this
> > code in place (which allocates regions in a different address space
> > using __get_vm_area and __vmalloc_area)?
>
> I hope so. The old APIs are still in place. You will actually get lazy
> unmapping, but that should be a transparent change unless you have any
> issues with the aliasing.
>
x86_64 does this anyway, so if that's continuing to work, then it should
be fine.
r, Kyle
WARNING: multiple messages have this Message-ID (diff)
From: Kyle McMartin <kyle@mcmartin.ca>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-arch@vger.kernel.org
Subject: Re: [patch] mm: rewrite vmap layer
Date: Tue, 19 Aug 2008 23:32:50 -0400 [thread overview]
Message-ID: <20080820033249.GA19241@phobos.i.cabal.ca> (raw)
In-Reply-To: <20080819103952.GE16446@wotan.suse.de>
On Tue, Aug 19, 2008 at 12:39:52PM +0200, Nick Piggin wrote:
> > Second question - will ARMs separate module area still work with this
> > code in place (which allocates regions in a different address space
> > using __get_vm_area and __vmalloc_area)?
>
> I hope so. The old APIs are still in place. You will actually get lazy
> unmapping, but that should be a transparent change unless you have any
> issues with the aliasing.
>
x86_64 does this anyway, so if that's continuing to work, then it should
be fine.
r, Kyle
--
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>
next prev parent reply other threads:[~2008-08-20 3:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 13:32 [patch] mm: rewrite vmap layer Nick Piggin
2008-08-18 13:32 ` Nick Piggin
2008-08-19 0:24 ` Andrew Morton
2008-08-19 0:24 ` Andrew Morton
2008-08-19 7:37 ` Russell King
2008-08-19 7:37 ` Russell King
2008-08-19 10:39 ` Nick Piggin
2008-08-19 10:39 ` Nick Piggin
2008-08-20 3:32 ` Kyle McMartin [this message]
2008-08-20 3:32 ` Kyle McMartin
2008-08-19 10:02 ` Nick Piggin
2008-08-19 10:02 ` Nick Piggin
2008-08-19 14:42 ` Christoph Lameter
2008-08-19 14:42 ` Christoph Lameter
2008-08-20 9:02 ` Nick Piggin
2008-08-20 9:02 ` Nick Piggin
2008-08-20 14:03 ` Christoph Lameter
2008-08-20 14:03 ` Christoph Lameter
2008-08-20 16:22 ` Nick Piggin
2008-08-20 16:22 ` Nick Piggin
2008-08-20 16:50 ` Christoph Lameter
2008-08-20 16:50 ` Christoph Lameter
2008-08-20 16:59 ` Nick Piggin
2008-08-20 16:59 ` Nick Piggin
2008-08-20 17:05 ` Christoph Lameter
2008-08-20 17:05 ` Christoph Lameter
2008-08-20 17:48 ` Nick Piggin
2008-08-20 17:48 ` Nick Piggin
2008-08-21 7:19 ` Johannes Weiner
2008-08-21 7:19 ` Johannes Weiner
2008-08-21 13:13 ` Christoph Lameter
2008-08-21 13:13 ` Christoph Lameter
2008-09-05 3:06 ` Andrew Morton
2008-09-05 3:06 ` Andrew Morton
2008-09-07 12:06 ` Nick Piggin
2008-09-07 12:06 ` 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=20080820033249.GA19241@phobos.i.cabal.ca \
--to=kyle@mcmartin.ca \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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.