From: Michael Schmitz <schmitzmic@googlemail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michael Schmitz <schmitzmic@googlemail.com>,
Thorsten Glaser <tg@mirbsd.de>,
linux-m68k@vger.kernel.org
Subject: Re: build warnings
Date: Mon, 31 Jan 2011 14:49:06 +1300 [thread overview]
Message-ID: <4D461512.8080609@gmail.com> (raw)
In-Reply-To: <AANLkTimB1fpvMsSeTbRn5ZTU1NCpZpjrAXQ+xRShAsZN@mail.gmail.com>
Geert,
>>
>> Whatever the reason - the SLUB allocator either is buggy outright for m68k,
>> or we run into memory pressure a lot sooner than other architectures and the
>> VM subsystem needs optimizing for SLUB.
>>
>> I'd just replace the Debian default for the m68k kernels....
>>
>
> If switching from SLUB to SLAB fixes the problem, please enable
> CONFIG_SLUB_DEBUG and bring it up on lkml/with the SLUB people.
>
Can do that - I'll try and collect debug data from another case I know
has had trouble with SLUB. I'll probably have to build a custom kernel
for them and test that on the live mail server. Fun ... :-)
Cheers,
Michael
next prev parent reply other threads:[~2011-01-31 1:49 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 14:44 build warnings Thorsten Glaser
2011-01-13 19:24 ` Michael Schmitz
2011-01-13 20:55 ` Geert Uytterhoeven
2011-01-14 9:25 ` Thorsten Glaser
2011-01-14 12:17 ` Geert Uytterhoeven
2011-01-16 4:36 ` Michael Schmitz
2011-01-16 13:54 ` Thorsten Glaser
2011-01-16 21:26 ` Michael Schmitz
2011-01-16 22:29 ` Thorsten Glaser
2011-01-17 2:48 ` Michael Schmitz
2011-01-17 6:51 ` Geert Uytterhoeven
2011-01-17 19:50 ` Michael Schmitz
2011-01-17 20:14 ` Geert Uytterhoeven
2011-01-18 1:18 ` Michael Schmitz
2011-01-18 13:29 ` Geert Uytterhoeven
2011-01-18 23:54 ` Michael Schmitz
2011-01-19 7:59 ` Geert Uytterhoeven
2011-01-30 5:37 ` Michael Schmitz
2011-01-30 13:53 ` Thorsten Glaser
2011-01-30 18:57 ` Geert Uytterhoeven
2011-01-31 1:49 ` Michael Schmitz [this message]
2011-01-31 4:03 ` Finn Thain
2011-01-31 6:41 ` Michael Schmitz
2011-01-31 7:10 ` Geert Uytterhoeven
2011-02-05 23:41 ` Thorsten Glaser
2011-02-13 4:34 ` Michael Schmitz
2011-02-17 7:22 ` Michael Schmitz
2011-02-17 18:18 ` Thorsten Glaser
2011-03-13 7:34 ` Michael Schmitz
2011-03-13 10:37 ` Thorsten Glaser
2011-03-26 1:26 ` Michael Schmitz
2011-01-31 6:28 ` Michael Schmitz
2011-01-17 6:50 ` Michael Schmitz
-- strict thread matches above, loose matches on Subject: below --
2014-08-13 22:59 Build Warnings Nick Krause
2014-08-14 4:14 ` Nick Krause
2010-01-29 9:03 build warnings Michael Wookey
2010-01-29 11:02 ` Jeff King
2010-01-29 11:23 ` Erik Faye-Lund
2008-10-25 8:24 Johannes Berg
2008-10-27 10:30 ` Tomas Winkler
2008-10-27 10:34 ` Johannes Berg
2008-10-27 10:41 ` Tomas Winkler
2008-10-27 13:28 ` John W. Linville
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=4D461512.8080609@gmail.com \
--to=schmitzmic@googlemail.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=tg@mirbsd.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.