This series sanitizes the interface to unmap_vma(). The crazy interface annoyed me no end when I was looking at unmap_single_vma(), which we can spend quite a lot of time in (especially with loads that have a lot of small fork/exec's: shell scripts etc). Moving the nr_accounted calculations to where they belong at least clarifies things a little. I hope to come back to look at the performance of this later, but if/when I get back to it I at least don't have to see the crazy interfaces any more. * vm-cleanups: vm: remove 'nr_accounted' calculations from the unmap_vmas() interfaces vm: simplify unmap_vmas() calling convention
Showing the changes to include (1 of 3 files). Show all
Unified · Split
| @@ -896,10 +896,8 @@ int zap_vma_ptes(struct vm_area_struct *vma, unsigned long address, · 895 unmodified lines | ||
| 896 | 896 | unsigned long size); |
| 897 | 897 | void zap_page_range(struct vm_area_struct *vma, unsigned long address, |
| 898 | 898 | unsigned long size, struct zap_details *); |
| 899 | −void unmap_vmas(struct mmu_gather *tlb, | |
| 900 | − struct vm_area_struct *start_vma, unsigned long start_addr, | |
| 901 | − unsigned long end_addr, unsigned long *nr_accounted, | |
| 902 | − struct zap_details *); | |
| 899 | +void unmap_vmas(struct mmu_gather *tlb, struct vm_area_struct *start_vma, | |
| 900 | + unsigned long start, unsigned long end); | |
| 903 | 901 | |
| 904 | 902 | /** |
| 905 | 903 | * mm_walk - callbacks for walk_page_range |