linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	linux-mm <linux-mm@kvack.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: inactive-clean list
Date: Tue, 25 Jul 2006 20:02:25 -0400	[thread overview]
Message-ID: <44C6B111.9010502@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0607251600001.32387@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> On Tue, 25 Jul 2006, Rik van Riel wrote:
> 
>>> An increment of a VM counter causes a state change in the hypervisor?
>> Christoph, please read more than the first 5 words in each
>> email before replying.
> 
> Well, I read the whole thing before I replied and I could not figure this 
> one out. Maybe I am too dumb to understand. Could you please explain 
> yourself in more detail

Page state transitions can be very expensive in a virtualized
environment, so it would be good if we had fewer transitions.

> I am also not sure why I should be running a hypervisor in the first place 
> and so I may not be up to date on the whole technology.

You may not, but IMHO it would be good if whatever new VM
things we implement in Linux would at least be virtualization
friendly.  Especially if that can be achieved without hurting
native performance...

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-07-26  0:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17 20:24 Peter Zijlstra
2006-07-18  3:37 ` Christoph Lameter
2006-07-18 12:16   ` Peter Zijlstra
2006-07-18 13:29     ` Christoph Lameter
2006-07-18 13:55       ` Martin J. Bligh
2006-07-18 13:59         ` Christoph Lameter
2006-07-18 15:12           ` Martin J. Bligh
2006-07-18 15:57             ` Christoph Lameter
2006-07-18 16:23               ` Martin J. Bligh
2006-07-18 14:03         ` Christoph Lameter
2006-07-18 14:25           ` Andrew Morton
2006-07-18 14:45             ` Christoph Lameter
2006-07-18 15:59               ` KAMEZAWA Hiroyuki
2006-07-23  5:50 ` Rik van Riel
2006-07-24 18:11   ` Christoph Lameter
2006-07-24 19:00     ` Rik van Riel
2006-07-25 20:25       ` Christoph Lameter
2006-07-25 21:37         ` Rik van Riel
2006-07-25 23:03           ` Christoph Lameter
2006-07-26  0:02             ` Rik van Riel [this message]
2006-07-26  0:05               ` Christoph Lameter
2006-07-26 11:00   ` Martin Schwidefsky
2006-07-26 11:11     ` Peter Zijlstra
2006-07-26 13:04       ` Martin Schwidefsky
2006-07-26 14:45         ` Peter Zijlstra
2006-07-27 11:16           ` Martin Schwidefsky
2006-07-26 15:41         ` 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=44C6B111.9010502@redhat.com \
    --to=riel@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --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