Re: [PATCHv2] mm/vmalloc: avoid soft lockup warnings when vunmap()'ing large ranges

2014-03-11 Thread Andrew Morton
On Tue, 11 Mar 2014 18:40:23 + David Vrabel wrote: > If vunmap() is used to unmap a large (e.g., 50 GB) region, it may take > sufficiently long that it triggers soft lockup warnings. > > Add a cond_resched() into vunmap_pmd_range() so the calling task may > be resheduled after unmapping

[PATCHv2] mm/vmalloc: avoid soft lockup warnings when vunmap()'ing large ranges

2014-03-11 Thread David Vrabel
If vunmap() is used to unmap a large (e.g., 50 GB) region, it may take sufficiently long that it triggers soft lockup warnings. Add a cond_resched() into vunmap_pmd_range() so the calling task may be resheduled after unmapping each PMD entry. This is how zap_pmd_range() fixes the same problem

[PATCHv2] mm/vmalloc: avoid soft lockup warnings when vunmap()'ing large ranges

2014-03-11 Thread David Vrabel
If vunmap() is used to unmap a large (e.g., 50 GB) region, it may take sufficiently long that it triggers soft lockup warnings. Add a cond_resched() into vunmap_pmd_range() so the calling task may be resheduled after unmapping each PMD entry. This is how zap_pmd_range() fixes the same problem

Re: [PATCHv2] mm/vmalloc: avoid soft lockup warnings when vunmap()'ing large ranges

2014-03-11 Thread Andrew Morton
On Tue, 11 Mar 2014 18:40:23 + David Vrabel david.vra...@citrix.com wrote: If vunmap() is used to unmap a large (e.g., 50 GB) region, it may take sufficiently long that it triggers soft lockup warnings. Add a cond_resched() into vunmap_pmd_range() so the calling task may be resheduled