linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Redelings I <bredelin@ucla.edu>
To: linux-mm@kvack.org
Subject: try_to_swap_out: to aggressive in dropping pte's?
Date: Mon, 17 Sep 2001 13:04:51 -0700	[thread overview]
Message-ID: <3BA65763.8090900@ucla.edu> (raw)

Hello,
	I was wondering if anybody could explain why we try to drop the pte on a 
page if it is not pte_young, even if it has a high age and has the 
referenced bit set?

	Also, does anybody have any thoughts on how to decouple scanning the page 
tables for hardward referenced bits, and doing swap-out?  On one of my 
128mb boxes, linus's changes to only run swap_out when there is memory 
pressure make things MUCH more interactive and decreased unnecessary 
swapping.  However, this means that the page tables are not scanned, 
which is not good...

	On a related note, in 2.4.10-pre10, Linus makes pages get deactivated in 
try_to_swap_out if !PageReferenced(page), thus making page->age almost 
irrelevant.  I would like to make a quick hack hybrid approach that 
keeps lots of the 2.4.10-pre10 vm changes still uses age information on 
the active list.  This probably isn't adequate, but how about:

1. change "if (ptep_test_and_clear_young(page_table))" to
"if (ptep_test_and_clear_young(page_table) ||
	PageTestandClearReference(page))"

2. revert Linus's change in pre10 to deactivate pages if age==0 instead 
of if !PageReference.

thanks for any suggestions,
-BenRI
-- 
"I will begin again" - U2, 'New Year's Day'
Benjamin Redelings I      <><     http://www.bol.ucla.edu/~bredelin/

--
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/

                 reply	other threads:[~2001-09-17 20:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3BA65763.8090900@ucla.edu \
    --to=bredelin@ucla.edu \
    --cc=linux-mm@kvack.org \
    /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