public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: clameter@engr.sgi.com
Cc: Hirokazu Takahashi <taka@valinux.co.jp>,
	rob@landley.net, akpm@osdl.org, torvalds@osdl.org,
	kravetz@us.ibm.com, raybry@mpdtxmail.amd.com,
	linux-kernel@vger.kernel.org, lee.schermerhorn@hp.com,
	haveblue@us.ibm.com, magnus.damm@gmail.com, pj@sgi.com,
	marcelo.tosatti@cyclades.com
Subject: Re: [PATCH 0/5] Swap Migration V5: Overview
Date: Wed, 02 Nov 2005 23:11:50 +0900	[thread overview]
Message-ID: <4368C926.2040102@jp.fujitsu.com> (raw)
In-Reply-To: <20051102.212651.25143264.taka@valinux.co.jp>

Hirokazu Takahashi wrote:
> Hi Christoph,
> I've read the archive of lhms-devel.
> You're going to take in most of the original migration code
> except for some tricks to migrate pages which are hard to move.
> I think this is what you said the complexity, which you
> want to remove forever.
> 
> I have to explain that this complexity came from making the code
> guarantee to be able to migrate any pages. So the code is designed:
>   - to migrate heavily accessed pages.
>   - to migrate pages without backing-store.
>   - to migrate pages without I/O's.
>   - to migrate pages of which status may be changed during the migration
>     correctly.
> 
> This have to be implemented if the hotplug memory use it.
yes.

> It seems to become a reinvention of the wheel to me.
> 
Christoph, I think you should make it clear the advantage of your code
to the -mhp tree's. I think we can add migrate_page_to() easily to the
-mhp tree's as Takahashi said.

BTW, could you explain what is done and what is not in your patch set ?

-- Kame




  parent reply	other threads:[~2005-11-02 14:14 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01  3:12 [PATCH 0/5] Swap Migration V5: Overview Christoph Lameter
2005-11-01  3:12 ` [PATCH 1/5] Swap Migration V5: LRU operations Christoph Lameter
2005-11-07  7:35   ` Magnus Damm
2005-11-07 17:41     ` Christoph Lameter
2005-11-07 18:12       ` Christoph Lameter
2005-11-15  5:44   ` Andrew Morton
2005-11-15 16:38     ` Christoph Lameter
2005-11-15 16:43       ` SKB tutorial, Blog, and NET TODO Surya Satyavolu
2005-11-15 18:02       ` [PATCH 1/5] Swap Migration V5: LRU operations Andrew Morton
2005-11-15 18:22         ` Christoph Lameter
2005-11-15 18:46           ` Andrew Morton
2005-12-31  7:32             ` Marcelo Tosatti
2005-11-15 18:08       ` Lee Schermerhorn
2005-11-01  3:12 ` [PATCH 2/5] Swap Migration V5: PF_SWAPWRITE to allow writing to swap Christoph Lameter
2005-11-01  3:12 ` [PATCH 3/5] Swap Migration V5: migrate_pages() function Christoph Lameter
2005-11-01  8:06   ` Rob Landley
2005-11-01  8:59     ` Dave Hansen
2005-11-01  3:12 ` [PATCH 4/5] Swap Migration V5: MPOL_MF_MOVE interface Christoph Lameter
2005-11-01  3:13 ` [PATCH 5/5] Swap Migration V5: sys_migrate_pages interface Christoph Lameter
2005-11-01  5:27   ` Andrew Morton
2005-11-01 12:00     ` linux-os (Dick Johnson)
2005-11-01 18:10       ` Christoph Lameter
2005-11-01 17:39     ` Christoph Lameter
2005-11-01  3:25 ` [PATCH 0/5] Swap Migration V5: Overview Andrew Morton
2005-11-01  8:08   ` Rob Landley
2005-11-01 17:44     ` Christoph Lameter
2005-11-02  5:30       ` Hirokazu Takahashi
2005-11-02  8:31         ` Christoph Lameter
2005-11-02  8:45           ` Hirokazu Takahashi
2005-11-02 12:26           ` Hirokazu Takahashi
2005-11-02 13:08             ` Hirokazu Takahashi
2005-11-02 14:11             ` Kamezawa Hiroyuki [this message]
2005-11-02 15:48             ` Christoph Lameter
2005-11-02 20:00     ` Christoph Lameter
2005-11-01 10:22   ` KAMEZAWA Hiroyuki
2005-11-01 17:19   ` Christoph Lameter

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=4368C926.2040102@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=akpm@osdl.org \
    --cc=clameter@engr.sgi.com \
    --cc=haveblue@us.ibm.com \
    --cc=kravetz@us.ibm.com \
    --cc=lee.schermerhorn@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=pj@sgi.com \
    --cc=raybry@mpdtxmail.amd.com \
    --cc=rob@landley.net \
    --cc=taka@valinux.co.jp \
    --cc=torvalds@osdl.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