Hi, I'd like some feedback about this patchset -- whether it is the right design, and the implementation (e.g. people might dislike patch 4). vm_insert_page and remap_pfn_range loops are really clever, bit probably asking a bit too much of most drivers. I was able to get rid of most of them without too much trouble. Not tested, because I don't have any of the hardware, but it seems compiles OK. Nick - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [patch 0/5] mm: improve remapping of vmalloc regions
- From: Nick Holloway <[email protected]>
- [patch][rfc] improve remap_vmalloc_range callers' return values
- From: Nick Piggin <[email protected]>
- [patch 6/5] mm: find_vm_area locking fixes
- From: Nick Piggin <[email protected]>
- [patch 5/5] drivers: leave vm_flags alone
- From: Nick Piggin <[email protected]>
- [patch 1/5] mm: remap_vmalloc_range
- From: Nick Piggin <[email protected]>
- [patch 3/5] mm: remove rvmalloc
- From: Nick Piggin <[email protected]>
- [patch 2/5] mm: deprecate vmalloc_to_pfn
- From: Nick Piggin <[email protected]>
- [patch 4/5] mm: extra remap_vmalloc_range check
- From: Nick Piggin <[email protected]>
- Re: [patch 0/5] mm: improve remapping of vmalloc regions
- Prev by Date: Re: BUG at drivers/md/kcopyd.c:146 (was: [PATCH 1/9] device-mapper snapshot: load metadata on creation)
- Next by Date: [patch 4/5] mm: extra remap_vmalloc_range check
- Previous by thread: [PATCH 1/7] FS-Cache: Provide a filesystem-specific sync'able page bit
- Next by thread: [patch 4/5] mm: extra remap_vmalloc_range check
- Index(es):