From: Peter Xu <peterx@redhat.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
peterx@redhat.com, Matthew Wilcox <willy@infradead.org>
Subject: [PATCH 0/3] mm/smaps: Fixes and optimizations on shmem swap handling
Date: Fri, 17 Sep 2021 12:47:53 -0400 [thread overview]
Message-ID: <20210917164756.8586-1-peterx@redhat.com> (raw)
This series grows from the patch previously posted here:
[PATCH] mm/smaps: Use vma->vm_pgoff directly when counting partial swap
https://lore.kernel.org/lkml/20210916215839.95177-1-peterx@redhat.com/
Vlastimil reported a bug that is even more important to fix than the cleanup,
so I put it as patch 1 here. There's a test program we can use to verify the
bug before/after the patch. I used the same program to test patch 2/3 because
it covers walking shmem swap both in page cache and in pgtables.
Patch 2 is the original patch, though with a tiny touchup as Vlastimil
suggested.
Patch 3 is a further cleanup of the shmem swap logic, hopefully make it even
cleaner.
Please review, thanks.
Peter Xu (3):
mm/smaps: Fix shmem pte hole swap calculation
mm/smaps: Use vma->vm_pgoff directly when counting partial swap
mm/smaps: Simplify shmem handling of pte holes
fs/proc/task_mmu.c | 28 ++++++++++++++++------------
mm/shmem.c | 5 ++---
2 files changed, 18 insertions(+), 15 deletions(-)
--
2.31.1
next reply other threads:[~2021-09-17 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 16:47 Peter Xu [this message]
2021-09-17 16:47 ` [PATCH 1/3] mm/smaps: Fix shmem pte hole swap calculation Peter Xu
2021-09-22 10:40 ` Vlastimil Babka
2021-09-17 16:47 ` [PATCH 2/3] mm/smaps: Use vma->vm_pgoff directly when counting partial swap Peter Xu
2021-09-22 10:41 ` Vlastimil Babka
2021-09-17 16:47 ` [PATCH 3/3] mm/smaps: Simplify shmem handling of pte holes Peter Xu
2021-10-05 11:15 ` Vlastimil Babka
2021-10-05 14:40 ` Peter Xu
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=20210917164756.8586-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).