From: Russell King <rmk@arm.linux.org.uk>
To: Hugh Dickins <hugh@veritas.com>
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:42:28 +0100 [thread overview]
Message-ID: <20040418134228.B12222@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0404181331240.20000-100000@localhost.localdomain>; from hugh@veritas.com on Sun, Apr 18, 2004 at 01:36:11PM +0100
On Sun, Apr 18, 2004 at 01:36:11PM +0100, Hugh Dickins wrote:
> 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.
Well, having struggled with the kernels include mess to try to get at
the information I need to flush the TLB from an asm-arm header file,
I'm just considering whether to just say "fuck it" and add
#ifdef __arm__
flush_tlb_mm_page(ptep_to_mm(pte), ptep_to_address(pte));
#endif
directly into page_referenced() and be done with it.
Basically, to be able to use either ptep_to_mm() or ptep_to_address()
in asm/pgtable.h, you need to:
1. remove linux/mm.h from asm-generic/rmap.h
2. somehow work around linux/highmem.h which includes linux/mm.h so
asm-generic/rmap.h can have a definition of kmap_atomic_to_page()
3. remove asm/pgtable.h from linux/mm.h and linux/page-flags.h
I've managed to get so far with that, but the real killer seems to
be (2).
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
--
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:42 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
2004-04-18 12:42 ` Russell King [this message]
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=20040418134228.B12222@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--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