linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: David Howells <dhowells@redhat.com>
Cc: clameter@sgi.com, mpm@selenic.com, linux-mm@kvack.org
Subject: Re: Slab initialisation problems on MN10300
Date: Mon, 18 Feb 2008 19:37:53 +0200	[thread overview]
Message-ID: <84144f020802180937p6bea0a25t93b8f9c7202b06e2@mail.gmail.com> (raw)
In-Reply-To: <84144f020802180918h6fb4d52fw4c592407a16b19c0@mail.gmail.com>

Hi,

On Feb 18, 2008 7:18 PM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> 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.

Hmm, I double-checked the patch and it probably isn't the cause here.
It's just that we haven't changed SLAB bootstrap all that much except
for this patch. One thing that I thought of was ARCH_KMALLOC_MINALIGN
which is set to some fairly big values on some MIPS architectures
(MN10300 is one, right?) but reading the code I wasn't able to see
what could go wrong with that either...

--
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:[~2008-02-18 17:37 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 [this message]
2008-02-18 20:39   ` David Howells
2008-02-18 20:38 ` David Howells
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=84144f020802180937p6bea0a25t93b8f9c7202b06e2@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=clameter@sgi.com \
    --cc=dhowells@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=mpm@selenic.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).