linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, kamezawa.hiroyu@jp.fujitsu.com,
	lee.schermerhorn@hp.com, hugh@veritas.com
Subject: Re: [PATCH 1/7] page migration: Reorder functions in migrate.c
Date: Fri, 28 Apr 2006 15:08:06 -0700	[thread overview]
Message-ID: <20060428150806.057b0bac.akpm@osdl.org> (raw)
In-Reply-To: <20060428060302.30257.76871.sendpatchset@schroedinger.engr.sgi.com>

Christoph Lameter <clameter@sgi.com> wrote:
>
> page migration: Reorder functions in migrate.c

I'm a bit concerned about the way these migration patches are shaping up.

- There was quite a lot of rework against the initial batch of "swapless"
  patches.  I haven't yet found the time to sit down and review the end
  result.

- The initial batch of "swapless" patches needed a whole barrage of
  fixups to make the kernel compile.

- The patch series is rather straggly now: later patches are fixing up
  code which was added in multiple earlier patches, so refactoring it all
  logically is non-trivial.

- I have vague feelings of disquiet regarding the whole thing and would
  like to find the time to sit down and take a closer look at what's going
  on in there.  This is a bit hard with the patches factored as they are
  now.

So I'm thinking it'd be good (for me, at least) if I were to drop the lot
and ask you to refactor the patch series back into a logical sequence, make
sure all the fixups are folded into the right places so we can generally
take a fresh look at what you're proposing.

How hurtful would that be?

--
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>

  parent reply	other threads:[~2006-04-28 22:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28  6:03 Christoph Lameter
2006-04-28  6:03 ` [PATCH 2/7] page migration: Remove unnecessarily exported functions Christoph Lameter
2006-04-28  6:03 ` [PATCH 3/7] page migration: Change handling of address spaces Christoph Lameter
2006-04-28  6:03 ` [PATCH 4/7] page migration: Drop nr_refs parameter Christoph Lameter
2006-04-28  7:30   ` KAMEZAWA Hiroyuki
2006-04-28 13:57     ` Christoph Lameter
2006-04-28  6:03 ` [PATCH 5/7] page migration: synchronize from and to lists Christoph Lameter
2006-04-28  7:46   ` KAMEZAWA Hiroyuki
2006-04-28 15:31     ` Christoph Lameter
2006-04-29  0:27       ` KAMEZAWA Hiroyuki
2006-04-29  0:33         ` Christoph Lameter
2006-04-29  0:44           ` KAMEZAWA Hiroyuki
2006-04-29  0:46             ` Christoph Lameter
2006-04-28  6:03 ` [PATCH 6/7] page migration: Extract try_to_unmap Christoph Lameter
2006-04-28  6:03 ` [PATCH 7/7] page migration: Add new fallback function Christoph Lameter
2006-04-28  6:42   ` Christoph Lameter
2006-04-28 22:08 ` Andrew Morton [this message]
2006-04-28 23:01   ` [PATCH 1/7] page migration: Reorder functions in migrate.c Christoph Lameter
2006-04-28 23:18     ` Andrew Morton
2006-04-29  0:14       ` Christoph Lameter
2006-04-29  0:36         ` Andrew Morton
2006-04-29  0:46           ` Christoph Lameter
2006-04-29  2:27             ` Andrew Morton
2006-04-29  2:48               ` Christoph Lameter
2006-04-29  0:54           ` 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=20060428150806.057b0bac.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=hugh@veritas.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=lee.schermerhorn@hp.com \
    --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