From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
balbir@linux.vnet.ibm.com,
Joachim Deguara <joachim.deguara@amd.com>,
Christoph Lameter <clameter@sgi.com>, Mel Gorman <mel@csn.ul.ie>,
Eric Whitney <eric.whitney@hp.com>
Subject: Update: [Automatic] NUMA replicated pagecache on 2.6.23-rc4-mm1
Date: Tue, 11 Sep 2007 16:52:42 -0400 [thread overview]
Message-ID: <1189543962.5036.97.camel@localhost> (raw)
In-Reply-To: <20070813074351.GA15609@wotan.suse.de>
[Balbir: see notes re: replication and memory controller below]
A quick update: I have rebased the automatic/lazy page migration and
replication patches to 23-rc4-mm1. If interested, you can find the
entire series that I push in the '070911' tarball at:
http://free.linux.hp.com/~lts/Patches/Replication/
I haven't gotten around to some of the things you suggested to address
the soft lockups. etc. I just wanted to keep the patches up to date.
In the process of doing a quick sanity test, I encountered an issue with
replication and the new memory controller patches. I had built the
kernel with the memory controller enabled. I encountered a panic in
reclaim, while attempting to "drop caches", because replication was not
"charging" the replicated pages and reclaim tried to deref a null
"page_container" pointer. [!!! new member in page struct !!!]
I added code to try_to_create_replica(), __remove_replicated_page() and
release_pcache_desc() to charge/uncharge where I thought appropriate
[replication patch # 02]. That seemed to solve the panic during drop
caches triggered reclaim. However, when I tried a more stressful load,
I hit another panic ["NaT Consumption" == ia64-ese for invalid pointer
deref, I think] in shrink_active_list() called from direct reclaim.
Still to be investigated. I wanted to give you and Balbir a heads up
about the interaction of memory controllers with page replication.
Later,
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:[~2007-09-11 20:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 8:42 [patch][rfc] 2.6.23-rc1 mm: NUMA replicated pagecache Nick Piggin
2007-07-27 8:42 ` Nick Piggin
2007-07-27 14:30 ` Lee Schermerhorn
2007-07-27 14:30 ` Lee Schermerhorn
2007-07-30 3:16 ` Nick Piggin
2007-07-30 3:16 ` Nick Piggin
2007-07-30 16:29 ` Lee Schermerhorn
2007-07-30 16:29 ` Lee Schermerhorn
2007-08-08 20:25 ` Lee Schermerhorn
2007-08-08 20:25 ` Lee Schermerhorn
2007-08-10 21:08 ` Lee Schermerhorn
2007-08-10 21:08 ` Lee Schermerhorn
2007-08-13 7:43 ` Nick Piggin
2007-08-13 7:43 ` Nick Piggin
2007-08-13 14:05 ` Lee Schermerhorn
2007-08-13 14:05 ` Lee Schermerhorn
2007-08-14 2:08 ` Nick Piggin
2007-08-14 2:08 ` Nick Piggin
2007-09-11 20:52 ` Lee Schermerhorn [this message]
2007-09-12 1:52 ` Update: [Automatic] NUMA replicated pagecache on 2.6.23-rc4-mm1 Balbir Singh
2007-09-12 13:48 ` Lee Schermerhorn
2007-09-12 14:08 ` Balbir Singh
2007-09-12 15:09 ` Kernel Panic - 2.6.23-rc4-mm1 ia64 - was Re: Update: [Automatic] NUMA replicated pagecache Lee Schermerhorn
2007-09-12 15:09 ` Lee Schermerhorn
2007-09-12 15:41 ` Andy Whitcroft
2007-09-12 15:41 ` Andy Whitcroft
2007-09-12 17:04 ` Lee Schermerhorn
2007-09-12 17:04 ` Lee Schermerhorn
2007-09-12 19:46 ` [PATCH] " Lee Schermerhorn
2007-09-12 19:46 ` Lee Schermerhorn
2007-09-12 21:23 ` Balbir Singh
2007-09-12 21:23 ` Balbir Singh
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=1189543962.5036.97.camel@localhost \
--to=lee.schermerhorn@hp.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=clameter@sgi.com \
--cc=eric.whitney@hp.com \
--cc=joachim.deguara@amd.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--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.