linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: rmk@arm.linux.org.uk
Cc: linux-mm@kvack.org
Subject: Re: pte_young/pte_mkold/pte_mkyoung
Date: Wed, 4 Apr 2001 17:13:44 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0104041711060.1126-100000@localhost.localdomain> (raw)
In-Reply-To: <200104041600.RAA01119@raistlin.arm.linux.org.uk>

On Wed, 4 Apr 2001 rmk@arm.linux.org.uk wrote:
> 
> We currently seem to have:
> 	2 references to pte_mkyoung()
> 	1 reference to pte_mkold()
> 	0 references to pte_young()
> 
> This tells me that we're no longer using the hardware page tables on x86
> for page aging, which leads me nicely on to the following question.
> 
> Are there currently any plans to use the hardware page aging bits in the
> future, and if there are, would architectures that don't have them be
> required to have them?
> 
> I'm asking this question because for some time (1.3 onwards), the ARM
> architecture has had some code to handle software emulation of the young
> and dirty bits.  If its not required, then I'd like to get rid of this
> software emulation.

You may be out of luck: mm/vmscan.c try_to_swap_out() has

	if (ptep_test_and_clear_young(page_table)) {

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.eu.org/Linux-MM/

  reply	other threads:[~2001-04-04 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-04 16:00 pte_young/pte_mkold/pte_mkyoung rmk
2001-04-04 16:13 ` Hugh Dickins [this message]
2001-04-04 16:15 ` pte_young/pte_mkold/pte_mkyoung Rik van Riel

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.21.0104041711060.1126-100000@localhost.localdomain \
    --to=hugh@veritas.com \
    --cc=linux-mm@kvack.org \
    --cc=rmk@arm.linux.org.uk \
    /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