[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221222104937.795d2a134ac59c8244d9912c@linux-foundation.org>
Date: Thu, 22 Dec 2022 10:49:37 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Yuanchu Xie <yuanchu@...gle.com>
Cc: Ivan Babrou <ivan@...udflare.com>,
Johannes Weiner <hannes@...xchg.org>,
Yu Zhao <yuzhao@...gle.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Steven Barrett <steven@...uorix.net>,
Brian Geffon <bgeffon@...gle.com>,
Oleksandr Natalenko <oleksandr@...alenko.name>,
Suren Baghdasaryan <surenb@...gle.com>,
Arnd Bergmann <arnd@...db.de>, Peter Xu <peterx@...hat.com>,
Hugh Dickins <hughd@...gle.com>,
Gaosheng Cui <cuigaosheng1@...wei.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH 1/2] mm: add vma_has_locality()
On Wed, 21 Dec 2022 22:13:40 -0800 Yuanchu Xie <yuanchu@...gle.com> wrote:
> From: Yu Zhao <yuzhao@...gle.com>
>
> Currently in vm_flags in vm_area_struct, both VM_SEQ_READ and
> VM_RAND_READ indicate a lack of locality in accesses to the vma. Some
> places that check for locality are missing one of them. We add
> vma_has_locality to replace the existing locality checks for clarity.
I'm all confused. Surely VM_SEQ_READ implies locality and VM_RAND_READ
indicates no-locality?
Powered by blists - more mailing lists