[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOUHufb=f1KUyXFGm7XjXJu8sp+pYrhUreiTe=ypqMnJbgwGKg@mail.gmail.com>
Date: Fri, 7 Jul 2023 23:47:56 -0600
From: Yu Zhao <yuzhao@...gle.com>
To: Yin Fengwei <fengwei.yin@...el.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
ryan.roberts@....com, shy828301@...il.com,
akpm@...ux-foundation.org, willy@...radead.org, david@...hat.com
Subject: Re: [RFC PATCH 1/3] mm: add function folio_in_range()
On Fri, Jul 7, 2023 at 10:52 AM Yin Fengwei <fengwei.yin@...el.com> wrote:
>
> It will be used to check whether the folio is mapped to specific
> VMA and whether the mapping address of folio is in the range.
>
> Signed-off-by: Yin Fengwei <fengwei.yin@...el.com>
> ---
> mm/internal.h | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/mm/internal.h b/mm/internal.h
> index f1276d90484ad..66117523d7d71 100644
> --- a/mm/internal.h
> +++ b/mm/internal.h
> @@ -585,6 +585,32 @@ extern long faultin_vma_page_range(struct vm_area_struct *vma,
> bool write, int *locked);
> extern bool mlock_future_ok(struct mm_struct *mm, unsigned long flags,
> unsigned long bytes);
> +
> +static inline bool
> +folio_in_range(struct folio *folio, struct vm_area_struct *vma,
> + unsigned long start, unsigned long end)
Is there a caller that's not "folio_in_range(folio, vma,
vma->vm_start, vma->vm_end)"?
If not, then just "folio_within_vma(folio, vma)" or a wrapper on top
of folio_in_range().
Powered by blists - more mailing lists