From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: vmalloc: Return page array on vunmap
Date: Thu, 27 Mar 2008 23:22:20 +1100 [thread overview]
Message-ID: <200803272322.20493.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0803262117320.2794@schroedinger.engr.sgi.com>
On Thursday 27 March 2008 15:18, Christoph Lameter wrote:
> Make vunmap return the page array that was used at vmap. This is useful
> if one has no structures to track the page array but simply stores the
> virtual address somewhere. The disposition of the page array can then
> be decided upon by the caller after vunmap has torn down the mapping.
>
> vfree() may now also be used instead of vunmap. vfree() will release the
> page array after vunmap'ping it. If vfree() is called to free the page
> array then the page array must either be
>
> 1. Allocated via the slab allocator
>
> 2. Allocated via vmalloc but then VM_VPAGES must have been passed at
> vunmap to specify that a vfree is needed.
Is this really for something important? Because vmap/vunmap is so slow
and unscalable that it is pretty well unusable for any kind of dynamic
allocations. I have mostly rewritten it so it is a lot more scalable,
but all these little patches will make annoying rejects... Can it wait?
--
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-03-27 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 4:18 vmalloc: Return page array on vunmap, " Christoph Lameter, Christoph Lameter
2008-03-27 12:22 ` Nick Piggin [this message]
2008-03-27 18:48 ` Christoph Lameter
2008-03-27 23:02 ` Nick Piggin
2008-03-28 18:51 ` Christoph Lameter
2008-03-28 0:47 ` KAMEZAWA Hiroyuki
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=200803272322.20493.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--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