All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@sgi.com>
Cc: npiggin@suse.de, 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: Tue, 08 Aug 2006 11:24:47 +1000	[thread overview]
Message-ID: <44D7E7DF.1080106@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0608071556530.23088@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> If I take the following patches out then page migration works reliably 
> again. Otherwise page migration may result in weird values in the
> page struct. Reproduce by trying to migrate the executable pages
> of a running process. This usually creates enough races to break things.
> AFAIK the current radix tree rcu patches do not change the behavior
> of the tree_lock at all.
> 
> radix-tree-rcu-lockless-readside.patch
> redo-radix-tree-fixes.patch
> adix-tree-rcu-lockless-readside-update.patch
> radix-tree-rcu-lockless-readside-semicolon.patch
> adix-tree-rcu-lockless-readside-update-tidy.patch
> adix-tree-rcu-lockless-readside-fix-2.patch
> 
> Output in one failure scenario (after migrating the memory of cron back 
> and forth between nodes):

Yeah Lee noticed this as well...

Question: can you replace the lookup_slot with a regular lookup, then
replace the pointer switch with a radix_tree_delete + radix_tree_insert
and see if that works?

Thanks,
Nick

-- 
SUSE Labs, Novell Inc.
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>

  reply	other threads:[~2006-08-08  1:24 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 [this message]
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

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=44D7E7DF.1080106@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=clameter@sgi.com \
    --cc=lee.schermerhorn@hp.com \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    /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.