From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2.6.18-rc6.mm2] revert migrate_move_mapping to use direct radix tree slot update
Date: Wed, 13 Sep 2006 17:40:22 -0400 [thread overview]
Message-ID: <1158183622.5328.61.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0609131344450.19101@schroedinger.engr.sgi.com>
On Wed, 2006-09-13 at 13:48 -0700, Christoph Lameter wrote:
> On Wed, 13 Sep 2006, Lee Schermerhorn wrote:
>
> > Now that the problem with the rcu radix tree replace slot function has
> > been fixed, we can, if Christoph agrees:
>
> Instead of a new patch we could simply drop the patch
>
> page-migration-replace-radix_tree_lookup_slot-with-radix_tree_lockup.patch
>
> from Andrew's tree.
If you want to do it that way, I'll need to supply another patch to
clean up the compiler warnings [I think they were just warnings]
resulting from the change [at your suggestion ;-)] in the interface to
the radix tree functions.
Lee
WARNING: multiple messages have this Message-ID (diff)
From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2.6.18-rc6.mm2] revert migrate_move_mapping to use direct radix tree slot update
Date: Wed, 13 Sep 2006 17:40:22 -0400 [thread overview]
Message-ID: <1158183622.5328.61.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0609131344450.19101@schroedinger.engr.sgi.com>
On Wed, 2006-09-13 at 13:48 -0700, Christoph Lameter wrote:
> On Wed, 13 Sep 2006, Lee Schermerhorn wrote:
>
> > Now that the problem with the rcu radix tree replace slot function has
> > been fixed, we can, if Christoph agrees:
>
> Instead of a new patch we could simply drop the patch
>
> page-migration-replace-radix_tree_lookup_slot-with-radix_tree_lockup.patch
>
> from Andrew's tree.
If you want to do it that way, I'll need to supply another patch to
clean up the compiler warnings [I think they were just warnings]
resulting from the change [at your suggestion ;-)] in the interface to
the radix tree functions.
Lee
--
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>
next prev parent reply other threads:[~2006-09-13 21:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 19:09 [PATCH 2.6.18-rc6.mm2] revert migrate_move_mapping to use direct radix tree slot update Lee Schermerhorn
2006-09-13 19:09 ` Lee Schermerhorn
2006-09-13 20:48 ` Christoph Lameter
2006-09-13 20:48 ` Christoph Lameter
2006-09-13 21:40 ` Lee Schermerhorn [this message]
2006-09-13 21:40 ` Lee Schermerhorn
2006-09-13 21:43 ` Christoph Lameter
2006-09-13 21:43 ` 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=1158183622.5328.61.camel@localhost \
--to=lee.schermerhorn@hp.com \
--cc=akpm@osdl.org \
--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 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.