From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org, riel@surriel.com
Subject: Re: Page aging broken in 2.6
Date: Fri, 26 Dec 2003 09:33:56 +0000 [thread overview]
Message-ID: <20031226093356.A8980@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20031225234023.20396cbc.akpm@osdl.org>; from akpm@osdl.org on Thu, Dec 25, 2003 at 11:40:23PM -0800
On Thu, Dec 25, 2003 at 11:40:23PM -0800, Andrew Morton wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> > And we never flush the TLB entry.
> >
> > I don't know if x86 (or other archs really using page tables) will
> > actually set the referenced bit again in the PTE if it's already set
> > in the TLB, if not, then x86 needs a flush too.
>
> x86 needs a flush_tlb_page(), yes.
>
> > ppc and ppc64 need a flush to evict the entry from the hash table or
> > we'll never set the _PAGE_ACCESSED bit anymore.
ARM would strictly need the flush as well. I seem to vaguely remember,
however, that when this code went in there was some discussion about
this very topic, and it was decided that the flush was not critical.
Indeed, 2.4 seems to have the same logic concerning not flushing the
PTE:
/* Don't look at this pte if it's been accessed recently. */
if ((vma->vm_flags & VM_LOCKED) || ptep_test_and_clear_young(page_table)) {
mark_page_accessed(page);
return 0;
}
--
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
next prev parent reply other threads:[~2003-12-26 9:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-26 7:28 Page aging broken in 2.6 Benjamin Herrenschmidt
2003-12-26 7:40 ` Andrew Morton
2003-12-26 9:21 ` Arjan van de Ven
2003-12-26 9:58 ` Benjamin Herrenschmidt
2003-12-26 19:44 ` Davide Libenzi
2003-12-26 9:33 ` Russell King [this message]
2003-12-26 10:07 ` Benjamin Herrenschmidt
2003-12-26 17:59 ` Linus Torvalds
2003-12-26 23:55 ` Benjamin Herrenschmidt
2003-12-27 0:35 ` Linus Torvalds
2003-12-27 0:44 ` Benjamin Herrenschmidt
2003-12-27 0:53 ` Linus Torvalds
2003-12-27 0:59 ` Linus Torvalds
2003-12-27 1:03 ` Benjamin Herrenschmidt
2003-12-27 2:37 ` Andrea Arcangeli
2003-12-27 5:02 ` Benjamin Herrenschmidt
2003-12-27 10:16 ` William Lee Irwin III
2003-12-27 2:47 ` Rik van Riel
2003-12-27 3:00 ` Andrew Morton
2003-12-27 3:31 ` Rik van Riel
2003-12-27 3:54 ` Linus Torvalds
2003-12-27 16:34 ` Martin J. Bligh
2003-12-27 23:07 ` Roger Luethi
2003-12-27 23:55 ` William Lee Irwin III
2003-12-28 11:23 ` Roger Luethi
2003-12-28 16:35 ` William Lee Irwin III
2003-12-28 17:15 ` Roger Luethi
2003-12-28 0:04 ` Andrew Morton
2003-12-28 11:58 ` Roger Luethi
2003-12-27 1:41 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2003-12-26 10:45 Manfred Spraul
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=20031226093356.A8980@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@surriel.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