public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Rik van Riel <riel@redhat.com>,
	balbir@linux.vnet.ibm.com, jdike@addtoit.com,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	avi@redhat.com
Subject: Re: [PATCH] emulate accessed bit for EPT
Date: Fri, 5 Feb 2010 15:34:23 -0200	[thread overview]
Message-ID: <20100205173422.GA14706@amt.cnet> (raw)
In-Reply-To: <20100204174715.GL5959@random.random>

On Thu, Feb 04, 2010 at 06:47:15PM +0100, Andrea Arcangeli wrote:
> On Thu, Feb 04, 2010 at 08:40:43AM -0500, Rik van Riel wrote:
> > I suspect it won't be very many. I have been monitoring
> > /proc/meminfo on my system while testing this patch, and
> > it is quite typical that the size of the inactive anon
> > list does not change for minutes at a time.
> > 
> > In other words, no pages are moved onto or off of the
> > inactive anon list for several minutes. That corresponds
> > to a very small number of minor faults introduced by my
> > patch.
> 
> When there's light VM pressure, ideally there should be zero overhead
> caused by the patch. When there is VM pressure this will avoid some
> unnecessary I/O which should outweight the minor faults. It should be
> a good default behavior.

Agree.

But perhaps a module parameter to turn accessed bit emulation off might
be handy in the future?

  reply	other threads:[~2010-02-05 17:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 21:11 [PATCH] emulate accessed bit for EPT Rik van Riel
2010-02-04  4:12 ` Balbir Singh
2010-02-04 13:40   ` Rik van Riel
2010-02-04 15:30     ` Balbir Singh
2010-02-04 15:41       ` Rik van Riel
2010-02-04 15:52         ` Balbir Singh
2010-02-04 17:47     ` Andrea Arcangeli
2010-02-05 17:34       ` Marcelo Tosatti [this message]
2010-02-05 18:14         ` Andrea Arcangeli
2010-02-07 19:21           ` Marcelo Tosatti
2010-02-04 16:17 ` Jeff Dike
2010-02-08 10:27 ` Avi Kivity

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=20100205173422.GA14706@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=avi@redhat.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=jdike@addtoit.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.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