From: Hugh Dickins <hugh@veritas.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: William Lee Irwin III <wli@holomorphy.com>, linux-mm@kvack.org
Subject: Re: PTE aging, ptep_test_and_clear_young() and TLB
Date: Sun, 18 Apr 2004 13:36:11 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0404181331240.20000-100000@localhost.localdomain> (raw)
In-Reply-To: <20040418122344.A11293@flint.arm.linux.org.uk>
On Sun, 18 Apr 2004, Russell King wrote:
>
> So, I think we definitely need the flush there. The available data
> so far from Marc appears to confirm this, and the theory surrounding
> ASID-based MMUs (which are coming on ARM) also require it.
I agree that we need to flush TLB more, that if we keep on ignoring a
hint forever then things go awry. I disagree that it needs to be done
so immediately, in the young/referenced/accessed case. But go ahead,
we can always optimize some of it out later on.
Hugh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-04-18 12:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-17 20:15 Russell King
2004-04-17 20:43 ` William Lee Irwin III
2004-04-18 9:36 ` Russell King
2004-04-18 9:39 ` William Lee Irwin III
2004-04-18 10:58 ` Hugh Dickins
2004-04-18 11:23 ` Russell King
2004-04-18 12:36 ` Hugh Dickins [this message]
2004-04-18 12:42 ` Russell King
2004-04-18 19:55 ` Russell King
2004-04-18 20:01 ` Russell King
2004-04-18 23:14 ` Hugh Dickins
2004-04-18 23:34 ` Russell King
2004-04-18 15:52 ` William Lee Irwin III
2004-04-18 10:42 ` Russell King
2004-04-18 15:12 ` William Lee Irwin III
2004-04-17 22:27 ` Hugh Dickins
2004-04-17 23:47 ` Anton Blanchard
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=Pine.LNX.4.44.0404181331240.20000-100000@localhost.localdomain \
--to=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=rmk@arm.linux.org.uk \
--cc=wli@holomorphy.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