Re: [PATCH] mm/mmap: leave adjust_next as virtual address instead of page frame number

2020-09-08 Thread Wei Yang
On Tue, Sep 08, 2020 at 05:31:22PM +0200, Vlastimil Babka wrote: >On 8/28/20 10:10 AM, Wei Yang wrote: >> Instead of convert adjust_next between virtual address and page frame >> number, let's just store the virtual address into adjust_next. > >IMHO more precisely/less confusing it's "bytes" and

Re: [PATCH] mm/mmap: leave adjust_next as virtual address instead of page frame number

2020-09-08 Thread Vlastimil Babka
On 8/28/20 10:10 AM, Wei Yang wrote: > Instead of convert adjust_next between virtual address and page frame > number, let's just store the virtual address into adjust_next. IMHO more precisely/less confusing it's "bytes" and "pages" instead of "virtual address" (which is absolute address, but

[PATCH] mm/mmap: leave adjust_next as virtual address instead of page frame number

2020-08-28 Thread Wei Yang
Instead of convert adjust_next between virtual address and page frame number, let's just store the virtual address into adjust_next. Also, this patch fixes one typo in the comment of vma_adjust_trans_huge(). Signed-off-by: Wei Yang --- mm/huge_memory.c | 4 ++-- mm/mmap.c| 8