From: Linus Torvalds <torvalds@linux-foundation.org>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Linux-MM <linux-mm@kvack.org>, Bibo Mao <maobibo@loongson.cn>
Subject: Re: [PATCH v3 0/3] mm: improve pte updates and dirty/accessed
Date: Sun, 20 Dec 2020 10:00:06 -0800 [thread overview]
Message-ID: <CAHk-=wgEa8MrxrDUFs8H1E_fL6GngWbh+vcgtnsHD4nvRp4d_w@mail.gmail.com> (raw)
In-Reply-To: <20201220045535.848591-1-npiggin@gmail.com>
On Sat, Dec 19, 2020 at 8:55 PM Nicholas Piggin <npiggin@gmail.com> wrote:
>
> 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.
Looks ok to me. I'm surprised it's all that noticeable, but I don't
see anything worrisome in the patches.
Linus
prev parent reply other threads:[~2020-12-20 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 4:55 Nicholas Piggin
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 ` Linus Torvalds [this message]
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='CAHk-=wgEa8MrxrDUFs8H1E_fL6GngWbh+vcgtnsHD4nvRp4d_w@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=maobibo@loongson.cn \
--cc=npiggin@gmail.com \
/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