Re: [PATCH 05/30] mm/rmap: update mm/interval_tree.c comments
Pedro Falcato <[email protected]> Tue, 30 Jun 2026 17:16:51 +0100
| Newsgroups | org.kernel.vger.linux-sgx,dev.linux.lists.damon,dev.linux.lists.iommu,dev.linux.lists.nvdimm,org.freedesktop.lists.dri-devel,org.kernel.vger.kvm,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-parisc,org.kernel.vger.linux-perf-users,org.kernel.vger.linux-tegra,org.kernel.vger.linux-trace-kernel,org.kvack.linux-mm |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Jun 29, 2026 at 01:23:16PM +0100, Lorenzo Stoakes wrote: > Update the file comment to clarify that both file-backed and anonymous > interval trees are provided, referencing the relevant data types for > clarity. > > Also add comments to indicate which parts of the file apply to each. > > While we're here, convert the VM_BUG_ON_VMA() to VM_WARN_ON_ONCE_VMA(). > > Signed-off-by: Lorenzo Stoakes <[email protected]> Reviewed-by: Pedro Falcato <[email protected]> This is fine for now, but I'm wondering if it doesn't make sense to, in the long term, have: mm/rmap.c - common rmap mechanisms mm/anon_rmap.c - anon rmap gunk mm/file_rmap.c - file rmap gunk or even something like mm/rmap/{core,anon,file,ksm??}.c While working on my file rmap patches I noticed there's so much stuff just splurged all over rmap.c - interval_tree.c - fs.h - fs/inode.c. It's a little silly. -- Pedro