Re: [PATCH 1/9] mm/rmap: recompute pgoff for huge page

2013-12-02 Thread Joonsoo Kim
On Mon, Dec 02, 2013 at 02:44:34PM -0800, Andrew Morton wrote: > On Thu, 28 Nov 2013 16:48:38 +0900 Joonsoo Kim wrote: > > > We have to recompute pgoff if the given page is huge, since result based > > on HPAGE_SIZE is not approapriate for scanning the vma interval tree, as > > shown by commit 36

Re: [PATCH 1/9] mm/rmap: recompute pgoff for huge page

2013-12-02 Thread Andrew Morton
On Thu, 28 Nov 2013 16:48:38 +0900 Joonsoo Kim wrote: > We have to recompute pgoff if the given page is huge, since result based > on HPAGE_SIZE is not approapriate for scanning the vma interval tree, as > shown by commit 36e4f20af833 ("hugetlb: do not use vma_hugecache_offset() > for vma_prio_tr

Re: [PATCH 1/9] mm/rmap: recompute pgoff for huge page

2013-12-02 Thread Naoya Horiguchi
On Thu, Nov 28, 2013 at 04:48:38PM +0900, Joonsoo Kim wrote: > We have to recompute pgoff if the given page is huge, since result based > on HPAGE_SIZE is not approapriate for scanning the vma interval tree, as > shown by commit 36e4f20af833 ("hugetlb: do not use vma_hugecache_offset() > for vma_pr

[PATCH 1/9] mm/rmap: recompute pgoff for huge page

2013-11-27 Thread Joonsoo Kim
We have to recompute pgoff if the given page is huge, since result based on HPAGE_SIZE is not approapriate for scanning the vma interval tree, as shown by commit 36e4f20af833 ("hugetlb: do not use vma_hugecache_offset() for vma_prio_tree_foreach") and commit 369a713e ("rmap: recompute pgoff for unm