From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Suren Baghdasaryan <surenb@google.com>, akpm@linux-foundation.org
Cc: liam@infradead.org, ljs@kernel.org, vbabka@kernel.org,
willy@infradead.org, jannh@google.com, paulmck@kernel.org,
pfalcato@suse.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2 4/5] proc/task_mmu: read proc/pid/smaps_rollup under per-vma lock
Date: Wed, 9 Sep 2026 19:23:16 +0200 [thread overview]
Message-ID: <19e428e5-d8bc-4abb-b052-e23442464cba@kernel.org> (raw)
In-Reply-To: <20260907063918.3432401-5-surenb@google.com>
> - vma_start = vma->vm_start;
> - do {
> - smap_gather_stats(priv, vma, &mss, vma->vm_start);
> - last_vma_end = vma->vm_end;
> + if (!IS_ERR(vma) && vma != get_gate_vma(lock_ctx->mm))
> + vma_start = vma->vm_start;
> +
> + while (vma) {
> + if (IS_ERR(vma)) {
> + ret = PTR_ERR(vma);
> + goto out_unlock;
> + }
> +
Can we add a comment whey we break (and not e.g., continue) whenw e hit the gate
VMA?
(I seriously don't kmow ... should I know? :) )
> + if (vma == get_gate_vma(lock_ctx->mm))
> + break;
>
> /*
> - * Release mmap_lock temporarily if someone wants to
> - * access it for write request.
> + * If after retaking the lock, already reported VMA grew or
> + * merged with the next one, smap_gather_stats() will gather
> + * stats for the remaining portion by starting at last_vma_end.
> */
> - if (mmap_lock_is_contended(mm)) {
> - vma_iter_invalidate(&vmi);
> - unlock_ctx_mm(&priv->lock_ctx);
> - ret = lock_ctx_mm(&priv->lock_ctx);
> - if (ret) {
> - release_task_mempolicy(priv);
> - goto out_put_mm;
> - }
> + smap_gather_stats(priv, vma, &mss, last_vma_end);
> + last_vma_end = vma->vm_end;
I skimmed over the remaining bits, hoping the VMA lock experts will review in
detail :)
--
Cheers,
David
next prev parent reply other threads:[~2026-09-09 17:23 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 6:39 [PATCH v2 0/5] " Suren Baghdasaryan
2026-09-07 6:39 ` [PATCH v2 1/5] proc/task_mmu: remove unnecessary helpers Suren Baghdasaryan
2026-09-07 16:44 ` Usama Arif
2026-09-08 17:58 ` Liam R. Howlett
2026-09-09 17:06 ` David Hildenbrand (Arm)
2026-09-09 17:13 ` Suren Baghdasaryan
2026-09-09 17:17 ` David Hildenbrand (Arm)
2026-09-09 18:29 ` Suren Baghdasaryan
2026-09-10 15:43 ` Lorenzo Stoakes (ARM)
2026-09-07 6:39 ` [PATCH v2 2/5] proc/task_mmu: remove unnecessary inlines in function definitions Suren Baghdasaryan
2026-09-07 16:49 ` Usama Arif
2026-09-10 15:35 ` Suren Baghdasaryan
2026-09-08 18:01 ` Liam R. Howlett
2026-09-09 17:07 ` David Hildenbrand (Arm)
2026-09-09 17:15 ` Suren Baghdasaryan
2026-09-10 15:55 ` Lorenzo Stoakes (ARM)
2026-09-07 6:39 ` [PATCH v2 3/5] proc/task_mmu: remove special-casing of smap_gather_stats() start parameter Suren Baghdasaryan
2026-09-08 18:07 ` Liam R. Howlett
2026-09-09 17:16 ` David Hildenbrand (Arm)
2026-09-09 18:28 ` Suren Baghdasaryan
2026-09-09 19:16 ` David Hildenbrand (Arm)
2026-09-09 21:51 ` Suren Baghdasaryan
2026-09-10 7:41 ` David Hildenbrand (Arm)
2026-09-10 15:45 ` Suren Baghdasaryan
2026-09-10 16:01 ` David Hildenbrand (Arm)
2026-09-10 16:09 ` Suren Baghdasaryan
2026-09-10 16:21 ` Suren Baghdasaryan
2026-09-10 16:33 ` David Hildenbrand (Arm)
2026-09-10 17:02 ` Suren Baghdasaryan
2026-09-10 16:27 ` Lorenzo Stoakes (ARM)
2026-09-10 23:30 ` Suren Baghdasaryan
2026-09-07 6:39 ` [PATCH v2 4/5] proc/task_mmu: read proc/pid/smaps_rollup under per-vma lock Suren Baghdasaryan
2026-09-08 18:17 ` Liam R. Howlett
2026-09-09 14:25 ` Usama Arif
2026-09-09 16:13 ` Suren Baghdasaryan
2026-09-09 17:23 ` David Hildenbrand (Arm) [this message]
2026-09-09 17:58 ` Suren Baghdasaryan
2026-09-10 7:44 ` David Hildenbrand (Arm)
2026-09-10 21:20 ` Suren Baghdasaryan
2026-09-07 6:39 ` [PATCH v2 5/5] selftests/proc: add /proc/pid/smaps_rollup tearing tests Suren Baghdasaryan
2026-09-08 18:18 ` Liam R. Howlett
2026-09-08 16:04 ` [PATCH v2 0/5] read proc/pid/smaps_rollup under per-vma lock Xueyuan Chen
2026-09-08 16:08 ` Suren Baghdasaryan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19e428e5-d8bc-4abb-b052-e23442464cba@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=paulmck@kernel.org \
--cc=pfalcato@suse.de \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®