From: Ankita Garg <ankita@in.ibm.com>
To: Valdis.Kletnieks@vt.edu
Cc: linux-mm@kvack.org, svaidy@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] mm,debug: VM framework to capture memory reference pattern
Date: Wed, 6 Jul 2011 09:57:44 +0530 [thread overview]
Message-ID: <20110706042744.GA15861@in.ibm.com> (raw)
In-Reply-To: <64797.1309908804@turing-police.cc.vt.edu>
Hi,
On Tue, Jul 05, 2011 at 07:33:24PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 05 Jul 2011 13:52:34 +0530, Ankita Garg said:
>
> > by default) and scans through all pages of the specified tasks (including
> > children/threads) running in the system. If the hardware reference bit in the
> > page table is set, then the page is marked as accessed over the last sampling
> > interval and the reference bit is cleared.
>
> Does that cause any issues for other code in the mm subsystem that was
> expecting to use the reference bit for something useful? (Similarly, if other
> code in mm turns that bit *off* for its own reasons, does your code still
> produce useful results?)
At this point, the VM code does not use the reference bit for any
decision making, not even in the LRU. However, if the reference bit is
used later on, then this change will interfere with that logic.
--
Regards,
Ankita Garg (ankita@in.ibm.com)
Linux Technology Center
IBM India Systems & Technology Labs,
Bangalore, India
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-07-06 4:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 8:22 [PATCH 0/5] mm,debug: VM framework to capture memory reference pattern Ankita Garg
2011-07-05 8:22 ` [PATCH 1/5] Core kernel backend to capture the " Ankita Garg
2011-07-05 8:22 ` [PATCH 2/5] memref module to walk the process page table Ankita Garg
2011-07-05 8:22 ` [PATCH 3/5] Capture kernel memory references Ankita Garg
2011-07-05 8:22 ` [PATCH 4/5] Capture references to page cache pages Ankita Garg
2011-07-05 8:22 ` [PATCH 5/5] Logging the captured reference data Ankita Garg
2011-07-05 23:33 ` [PATCH 0/5] mm,debug: VM framework to capture memory reference pattern Valdis.Kletnieks
2011-07-06 4:27 ` Ankita Garg [this message]
2011-07-06 9:01 ` Andrew Morton
2011-07-06 9:31 ` Ankita Garg
2011-07-06 13:36 ` Matt Mackall
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=20110706042744.GA15861@in.ibm.com \
--to=ankita@in.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=svaidy@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).