From: Mel Gorman <mel@csn.ul.ie>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Christoph Lameter <clameter@sgi.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Nishanth Aravamudan <nacc@us.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm@kvack.org, lee.schermerhorn@hp.com, bob.picco@hp.com,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [BUG] at mm/slab.c:3320
Date: Sun, 20 Jan 2008 00:58:06 +0000 [thread overview]
Message-ID: <20080120005806.GA25669@csn.ul.ie> (raw)
In-Reply-To: <84144f020801170431l2d6d0d63i1fb7ebc5145539f4@mail.gmail.com>
On (17/01/08 14:31), Pekka Enberg didst pronounce:
> Hi Christoph,
>
> On Jan 10, 2008 2:02 AM, Christoph Lameter <clameter@sgi.com> wrote:
> > New patch that also checks in alternate_node_alloc if the node has normal
> > memory because we cannot call ____cache_alloc_node with an invalid node.
>
> [snip]
>
> > @@ -3439,8 +3442,14 @@ __do_cache_alloc(struct kmem_cache *cach
> > * We may just have run out of memory on the local node.
> > * ____cache_alloc_node() knows how to locate memory on other nodes
> > */
> > - if (!objp)
> > - objp = ____cache_alloc_node(cache, flags, numa_node_id());
> > + if (!objp) {
> > + int node_id = numa_node_id();
> > + if (likely(cache->nodelists[node_id])) /* fast path */
> > + objp = ____cache_alloc_node(cache, flags, node_id);
> > + else /* this function can do good fallback */
> > + objp = __cache_alloc_node(cache, flags, node_id,
> > + __builtin_return_address(0));
> > + }
>
> But __cache_alloc_node() will call fallback_alloc() that does
> cache_grow() for the node that doesn't have N_NORMAL_MEMORY, no?
>
> Shouldn't we just revert 04231b3002ac53f8a64a7bd142fde3fa4b6808c6 for
> 2.6.24 as this is a clear regression from 2.6.23?
>
I tried this patch and it didn't work out. Oops occured all in relation to
l3. I did see the obvious flaw and getting this close to 2.6.24 and the
other boot-problem on PPC64, I don't think we have the luxury of messing
around and maybe this should be tried again later? The minimum revert is
the following patch. I have verified it boots the machine in question.
===
Partial revert the changes made by 04231b3002ac53f8a64a7bd142fde3fa4b6808c6
to the kmem_list3 management. On a machine with a memoryless node, this
BUG_ON was triggering
static void *____cache_alloc_node(struct kmem_cache *cachep, gfp_t
flags,
int nodeid)
{
struct list_head *entry;
struct slab *slabp;
struct kmem_list3 *l3;
void *obj;
int x;
l3 = cachep->nodelists[nodeid];
BUG_ON(!l3);
Signed-off-by: Mel Gorman <mel@csn.ul.ie>
---
mm/slab.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff linux-2.6.24-rc8-015_remap_discontigmem/mm/slab.c linux-2.6.24-rc8-020_init_kmem3lists_nodes/mm/slab.c
--- linux-2.6.24-rc8-015_remap_discontigmem/mm/slab.c 2008-01-16 04:22:48.000000000 +0000
+++ linux-2.6.24-rc8-020_init_kmem3lists_nodes/mm/slab.c 2008-01-20 00:06:35.000000000 +0000
@@ -1590,7 +1590,7 @@ void __init kmem_cache_init(void)
/* Replace the static kmem_list3 structures for the boot cpu */
init_list(&cache_cache, &initkmem_list3[CACHE_CACHE], node);
- for_each_node_state(nid, N_NORMAL_MEMORY) {
+ for_each_online_node(nid) {
init_list(malloc_sizes[INDEX_AC].cs_cachep,
&initkmem_list3[SIZE_AC + nid], nid);
@@ -1968,7 +1968,7 @@ static void __init set_up_list3s(struct
{
int node;
- for_each_node_state(node, N_NORMAL_MEMORY) {
+ for_each_online_node(node) {
cachep->nodelists[node] = &initkmem_list3[index + node];
cachep->nodelists[node]->next_reap = jiffies +
REAPTIMEOUT_LIST3 +
@@ -3815,7 +3815,7 @@ static int alloc_kmemlist(struct kmem_ca
struct array_cache *new_shared;
struct array_cache **new_alien = NULL;
- for_each_node_state(node, N_NORMAL_MEMORY) {
+ for_each_online_node(node) {
if (use_alien_caches) {
new_alien = alloc_alien_cache(node, cachep->limit);
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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:[~2008-01-20 0:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 10:05 [BUG] at mm/slab.c:3320 Aneesh Kumar K.V
2007-12-25 22:05 ` Andrew Morton
2007-12-25 22:05 ` Andrew Morton
2007-12-27 15:32 ` Aneesh Kumar K.V
2007-12-27 15:32 ` Aneesh Kumar K.V
2007-12-27 19:31 ` Christoph Lameter
2007-12-27 19:31 ` Christoph Lameter
[not found] ` <20071228051959.GA6385@skywalker>
[not found] ` <Pine.LNX.4.64.0801021227580.20331@schroedinger.engr.sgi.com>
2008-01-03 15:50 ` Aneesh Kumar K.V
2008-01-04 0:33 ` Nishanth Aravamudan
2008-01-07 1:23 ` KAMEZAWA Hiroyuki
2008-01-07 18:10 ` Christoph Lameter
2008-01-08 1:40 ` KAMEZAWA Hiroyuki
2008-01-08 5:38 ` Christoph Lameter
2008-01-08 7:11 ` Aneesh Kumar K.V
2008-01-09 6:50 ` Nishanth Aravamudan
2008-01-09 17:50 ` Christoph Lameter
2008-01-09 18:58 ` Aneesh Kumar K.V
2008-01-09 19:23 ` Christoph Lameter
2008-01-09 21:47 ` Nishanth Aravamudan
2008-01-09 21:51 ` Christoph Lameter
2008-01-09 22:13 ` Nishanth Aravamudan
2008-01-10 0:02 ` Christoph Lameter
2008-01-17 12:31 ` Pekka Enberg
2008-01-17 14:32 ` Christoph Lameter
2008-01-17 14:36 ` Pekka J Enberg
2008-01-17 15:05 ` Christoph Lameter
2008-01-17 15:25 ` Aneesh Kumar K.V
2008-01-17 16:58 ` Christoph Lameter
2008-01-17 17:42 ` Aneesh Kumar K.V
2008-01-17 21:40 ` Mel Gorman
2008-01-17 20:47 ` Pekka J Enberg
2008-01-20 0:58 ` Mel Gorman [this message]
2008-01-22 20:20 ` Christoph Lameter
2008-01-10 4:13 ` Aneesh Kumar K.V
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=20080120005806.GA25669@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bob.picco@hp.com \
--cc=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=nacc@us.ibm.com \
--cc=penberg@cs.helsinki.fi \
/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.