All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Christoph Lameter <clameter@sgi.com>,
	linux-mm@kvack.org, Lee Schermerhorn <lee.schermerhorn@hp.com>
Subject: Re: 2.6.18-rc3-mm2: rcu radix tree patches break page migration
Date: Wed, 09 Aug 2006 11:39:28 +1000	[thread overview]
Message-ID: <44D93CD0.5070905@yahoo.com.au> (raw)
In-Reply-To: <20060808102511.64dcf5dc.akpm@osdl.org>

Andrew Morton wrote:

>On Tue, 8 Aug 2006 09:19:08 -0700 (PDT)
>Christoph Lameter <clameter@sgi.com> wrote:
>
>
>>The radix tree rcu code runs into trouble when we use radix_tree_lookup
>>slot and use the slot to update the page reference.
>>
>
>"trouble"?  Do we know what it is?  What are the implications of this for
>the rcu radix-tree patches?
>

I must have broken lookup_slot (luckily regular pagecache ops are not
affected). I'm looking at it...

--

Send instant messages to your online friends http://au.messenger.yahoo.com 

--
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-08-09  1:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 23:10 2.6.18-rc3-mm2: rcu radix tree patches break page migration Christoph Lameter
2006-08-08  1:24 ` Nick Piggin
2006-08-08  3:42   ` Christoph Lameter
2006-08-08  5:45     ` Nick Piggin
2006-08-08 14:53       ` Lee Schermerhorn
2006-08-08 16:19       ` Christoph Lameter
2006-08-08 17:25         ` Andrew Morton
2006-08-08 17:52           ` Christoph Lameter
2006-08-09  1:39           ` Nick Piggin [this message]

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=44D93CD0.5070905@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.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 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.