Thread (14 messages) 14 messages, 3 authors, 2006-04-20

Re: [patch 1/5] mm: remap_vmalloc_range

From: Nick Piggin <hidden>
Date: 2006-04-20 17:33:52
Also in: lkml

On Thu, Apr 20, 2006 at 06:22:05PM +0100, Christoph Hellwig wrote:
On Thu, Apr 20, 2006 at 07:06:18PM +0200, Nick Piggin wrote:
quoted
Add a remap_vmalloc_range and get rid of as many remap_pfn_range and
vm_insert_page loops as possible.

remap_vmalloc_range can do a whole lot of nice range checking even
if the caller gets it wrong (which it looks like one or two do).
This looks very nice, thanks!
Thank you
Although it might be better to split it
into one patch to introduce remap_vmalloc_range and various patches to
switch over one susbsyetm for merging purposes.
Sure, if anyone insists ;)

I tend to agree. I would tend to do it in just 2 patches
(1 for implementation, 1 for conversion) to make administrative
overheads smaller -- the conversions are small and very well
contained. Is there a good reason to split further?

Nick

--
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>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help