All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: dhowells@redhat.com, clameter@sgi.com, mpm@selenic.com,
	linux-mm@kvack.org
Subject: Re: Slab initialisation problems on MN10300
Date: Mon, 18 Feb 2008 20:38:31 +0000	[thread overview]
Message-ID: <24841.1203367111@redhat.com> (raw)
In-Reply-To: <84144f020802180918h6fb4d52fw4c592407a16b19c0@mail.gmail.com>

Pekka Enberg <penberg@cs.helsinki.fi> wrote:

> would put struct arraycache_init to kmalloc-32 and struct kmem_list3
> to kmalloc-64. So are INDEX_AC and INDEX_L3 really equivalent? To
> which cache do they refer to?

(gdb) p sizeof(struct arraycache_init)
$1 = 20
(gdb) p sizeof(struct kmem_list3)
$2 = 52

However, the compiler has eliminated the test:

		if (INDEX_AC == INDEX_L3)

even though it's compiled with -O0.

This is odd.  I'll have to investigate the preprocessor output.

> And if this broke recently, you might want to try and see if commit
> 556a169dab38b5100df6f4a45b655dddd3db94c1 ("slab: fix bootstrap on
> memoryless node") is at fault here by reverting it.

Well, the MN10300 arch worked in -mm, but no longer works now that the patches
have been merged into Linus's tree.  Bisecting is probably not an option.

Thanks, anyway.  I've got something to investigate.

David

--
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:[~2008-02-18 20:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 16:07 Slab initialisation problems on MN10300 David Howells
2008-02-18 17:18 ` Pekka Enberg
2008-02-18 17:37   ` Pekka Enberg
2008-02-18 20:39     ` David Howells
2008-02-18 20:38   ` David Howells [this message]
2008-02-18 20:57     ` Pekka Enberg
2008-02-18 22:41       ` David Howells
2008-02-18 23:02   ` David Howells

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=24841.1203367111@redhat.com \
    --to=dhowells@redhat.com \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.org \
    --cc=mpm@selenic.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.