From: Nicholas Piggin <npiggin@gmail.com>
To: linux-mm@kvack.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Bibo Mao <maobibo@loongson.cn>
Subject: [PATCH v3 0/3] mm: improve pte updates and dirty/accessed
Date: Sun, 20 Dec 2020 14:55:32 +1000 [thread overview]
Message-ID: <20201220045535.848591-1-npiggin@gmail.com> (raw)
Time to get this old series out again. Since last time, Bibo found a
couple of the same cases I did (for MIPS only) which I extend to all
archs, and I dropped the "make the pte dirty if the fork parent was
dirty" due to Linus pointing out a dirty PTE costs more to unmap. It
didn't seem to help a great deal anyway on the access-side fortunately.
Thanks,
Nick
Nicholas Piggin (3):
mm/cow: don't bother write protecting already write-protected huge
pages
mm/cow: optimise pte accessed bit handling in fork
mm: optimise pte dirty/accessed bit setting by demand based pte
insertion
arch/mips/include/asm/pgtable.h | 2 --
include/linux/pgtable.h | 16 ----------------
mm/huge_memory.c | 16 ++++++++++------
mm/hugetlb.c | 2 +-
mm/memory.c | 15 +++++++--------
mm/migrate.c | 1 +
mm/shmem.c | 1 +
mm/userfaultfd.c | 2 +-
mm/vmscan.c | 5 +++++
9 files changed, 26 insertions(+), 34 deletions(-)
--
2.23.0
next reply other threads:[~2020-12-20 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 4:55 Nicholas Piggin [this message]
2020-12-20 4:55 ` [PATCH v3 1/3] mm/cow: don't bother write protecting already write-protected huge pages Nicholas Piggin
2020-12-20 4:55 ` [PATCH v3 2/3] mm/cow: optimise pte accessed bit handling in fork Nicholas Piggin
2020-12-20 4:55 ` [PATCH v3 3/3] mm: optimise pte dirty/accessed bit setting by demand based pte insertion Nicholas Piggin
2020-12-21 18:21 ` Hugh Dickins
2020-12-22 3:24 ` Nicholas Piggin
2020-12-23 0:56 ` Huang Pei
2020-12-20 18:00 ` [PATCH v3 0/3] mm: improve pte updates and dirty/accessed Linus Torvalds
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=20201220045535.848591-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=linux-mm@kvack.org \
--cc=maobibo@loongson.cn \
--cc=torvalds@linux-foundation.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).