All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Bryant <raybry@sgi.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Hirokazu Takahashi <taka@valinux.co.jp>,
	Dave Hansen <haveblue@us.ibm.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: memory migration: bug in touch_unmapped_address
Date: Mon, 28 Feb 2005 12:56:40 -0600	[thread overview]
Message-ID: <42236968.9040807@sgi.com> (raw)
In-Reply-To: <20050228133348.GA26902@logos.cnet>

Marcelo Tosatti wrote:
> Good catch.
> 
> That was the reason for the migration cache problems you were seeing?
> 

AFAIK, no.  I found this problem because pages were being touched after
I scanned for pages to be migrated -- the result was that pages that
had not been touched by the application were being touched and then
left on the old nodes.

For the moment, I'm still pursuing a strategy of getting my manual
page migration code to work without the migration cache -- once I've
got that all working I'll come back and revisit the migration cache
bug I had reported.

-- 
Best Regards,
Ray
-----------------------------------------------
                   Ray Bryant
512-453-9679 (work)         512-507-7807 (cell)
raybry@sgi.com             raybry@austin.rr.com
The box said: "Requires Windows 98 or better",
            so I installed Linux.
-----------------------------------------------
--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2005-02-28 18:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-28 17:36 [PATCH] mm: memory migration: bug in touch_unmapped_address Ray Bryant
2005-02-28 13:33 ` Marcelo Tosatti
2005-02-28 18:56   ` Ray Bryant [this message]
2005-03-01  0:09 ` Hirokazu Takahashi

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=42236968.9040807@sgi.com \
    --to=raybry@sgi.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=taka@valinux.co.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.