From: pinotj@club-internet.fr
To: torvalds@osdl.org, nathans@sgi.com
Cc: neilb@cse.unsw.edu.au, manfred@colorfullife.com, akpm@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: Re: [Oops] i386 mm/slab.c (cache_flusharray)
Date: Fri, 5 Dec 2003 23:57:26 CET [thread overview]
Message-ID: <mnet1.1070665046.1802.pinotj@club-internet.fr> (raw)
>De: Linus Torvalds <torvalds@osdl.org>
[...]
>Jerome - can you test Nathan's patch together with my "avoid the
>complicated slab logic"? The slab avoidance thing got ext3 stable for you,
>now with Nathan's patch hopefully XFS will be stable too.
[...]
OK, I will do intensive tests this week-end, I have time. I just want to have some confirmations:
1. Is it still usefull to get all the backtraces of the last xfs oops ?
2. I will test patch-slab and patch-xfs on test11, CONFIG_DEBUG_PAGEALLOC (only). Test on XFS root and ext3 with "small" and "big" kernels.
3. What about patch-bio of Manfred ? I didn't have much time to try it yet but seems to stabilize too. Should I use it alone or with the others patchs ?
Thanks all for your help
Jerome Pinot
next reply other threads:[~2003-12-05 22:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 22:57 pinotj [this message]
2003-12-05 23:02 ` Re: [Oops] i386 mm/slab.c (cache_flusharray) Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2003-12-09 0:57 pinotj
2003-11-29 17:41 pinotj
2003-12-02 0:36 ` Linus Torvalds
2003-11-27 18:42 pinotj
2003-11-25 17:30 pinotj
2003-11-25 22:51 ` Linus Torvalds
2003-11-24 15:20 pinotj
2003-11-21 18:12 pinotj
2003-11-21 22:48 ` Linus Torvalds
2003-11-20 2:40 pinotj
2003-11-20 1:50 pinotj
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=mnet1.1070665046.1802.pinotj@club-internet.fr \
--to=pinotj@club-internet.fr \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=nathans@sgi.com \
--cc=neilb@cse.unsw.edu.au \
--cc=torvalds@osdl.org \
/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).