From: Tejun Heo <tj@kernel.org>
To: Torsten Kaiser <just.for.lkml@googlemail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: -mm: xfs lockdep warning
Date: Thu, 07 Oct 2010 16:05:23 +0200 [thread overview]
Message-ID: <4CADD3A3.5090401@kernel.org> (raw)
In-Reply-To: <AANLkTikRZZMq9GkaCn_BB7H=F0iGj3P-XbiaEU3RoN5V@mail.gmail.com>
Hello,
On 10/07/2010 03:21 PM, Torsten Kaiser wrote:
>> Can you test whether the following patch fix the issue?
>
> Yes. After adding this patch to 2.6.36-rc6 it survived my testcase. It
> first seems to get stuck again, but after less then a minute the
> system recovered and all compiles finished successfully.
>
> I suspect the combination of CFLAGs, the gcc version and maybe even
> changes in KOffice from 2.2.1 to 2.2.2 are import for my testcase. It
> looks like at the start of the complies something is really eating an
> enormous amount of memory and I did not hit such a case with earlier
> kernels.
It's great to hear that the patch helped but would you be able to
repeat the same test w/ 2.6.35 and see whether there's any noticeable
difference? Some level of stuttering is expected if the system is hit
with sudden huge spike of memory pressure but let's see if it has
regressed somehow.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-10-07 14:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 7:46 -mm: xfs lockdep warning Yang Ruirui
2010-09-16 7:46 ` Yang Ruirui
2010-09-17 0:52 ` Dave Chinner
2010-09-17 0:52 ` Dave Chinner
2010-09-20 19:13 ` Christoph Hellwig
2010-09-20 19:13 ` Christoph Hellwig
2010-09-25 13:08 ` Torsten Kaiser
2010-09-25 13:08 ` Torsten Kaiser
2010-10-04 9:01 ` Tejun Heo
2010-10-04 9:01 ` Tejun Heo
2010-10-04 9:21 ` Dave Chinner
2010-10-04 9:21 ` Dave Chinner
2010-10-05 10:09 ` Torsten Kaiser
2010-10-05 10:09 ` Torsten Kaiser
2010-10-05 16:51 ` Tejun Heo
2010-10-05 16:51 ` Tejun Heo
2010-10-05 16:55 ` Tejun Heo
2010-10-05 16:55 ` Tejun Heo
2010-10-05 18:09 ` Torsten Kaiser
2010-10-05 18:09 ` Torsten Kaiser
2010-10-05 18:17 ` Christoph Hellwig
2010-10-05 18:17 ` Christoph Hellwig
2010-10-05 17:54 ` Torsten Kaiser
2010-10-05 17:54 ` Torsten Kaiser
[not found] ` <AANLkTineNfy+hfnK-sjHNB+h05oC4qbJ+81pg95Bmn=b@mail.gmail.com>
[not found] ` <4CAC366E.7070609@kernel.org>
[not found] ` <4CAC38D9.8020407@kernel.org>
[not found] ` <AANLkTikw=ObzgWu35fsuriC-jVrzDRHRfFJeT8-4-ndY@mail.gmail.com>
[not found] ` <4CAC934E.2030807@kernel.org>
[not found] ` <AANLkTinrBeMDyQJaYJFALTPpOgEaAy7yoPdyQ0Gpay3G@mail.gmail.com>
[not found] ` <4CACC0CD.5000001@kernel.org>
2010-10-07 11:14 ` Tejun Heo
2010-10-07 13:21 ` Torsten Kaiser
2010-10-07 14:05 ` Tejun Heo [this message]
2010-10-07 15:15 ` Torsten Kaiser
2010-10-07 15:41 ` Tejun Heo
[not found] ` <AANLkTi=LnbH7LNUr+YuR+uKLFasKyV7hOZc1zD0qqHnW@mail.gmail.com>
2010-10-08 12:40 ` Tejun Heo
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=4CADD3A3.5090401@kernel.org \
--to=tj@kernel.org \
--cc=just.for.lkml@googlemail.com \
--cc=linux-kernel@vger.kernel.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 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.