From: Milan Broz <mbroz@redhat.com>
To: Alasdair G Kergon <agk@redhat.com>
Cc: Yan Li <elliot.li.tech@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ritesh Raj Sarraf <rrs@researchut.com>,
Christophe Saout <christophe@saout.de>,
linux-kernel@vger.kernel.org, dm-devel@redhat.com,
Herbert Xu <herbert@gondor.apana.org.au>,
rjmaomao@gmail.com, dm-crypt@saout.de
Subject: Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
Date: Fri, 06 Jun 2008 08:46:20 +0200 [thread overview]
Message-ID: <4848DD3C.9000001@redhat.com> (raw)
In-Reply-To: <20080605224410.GA7584@yantp.cn.ibm.com>
Yan Li wrote:
> On Mon, Jun 02, 2008 at 02:51:04PM +0200, Milan Broz wrote:
>> Patch for 2.6.24 kernel
>> Add cond_resched() to prevent stuck in big bio processing.
>
> This patch actual has lead to performance _gain_.
hmmm, nice:)
> With patched kernel, soft lockup _no longer_ occurred.
Alasdair, please could you move this patch back to actual tree
and sent it upstream?
We have at least two separate reports confirming that it fixes
the problem.
Milan
--
mbroz@redhat.com
next prev parent reply other threads:[~2008-06-06 6:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 13:54 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt Ritesh Raj Sarraf
2008-02-29 7:20 ` Andrew Morton
2008-02-29 18:15 ` Herbert Xu
2008-02-29 18:46 ` [dm-devel] " Alasdair G Kergon
2008-02-29 18:59 ` Ritesh Raj Sarraf
2008-03-01 19:30 ` Milan Broz
2008-03-01 19:33 ` Milan Broz
2008-03-01 21:59 ` Gunter Ohrner
2008-03-02 7:58 ` Gunter Ohrner
2008-03-06 14:41 ` [dm-devel] " Ritesh Raj Sarraf
2008-06-02 3:07 ` Yan Li
2008-06-02 6:52 ` Milan Broz
2008-06-02 12:31 ` Yan Li
2008-06-02 12:51 ` Milan Broz
2008-06-05 22:44 ` Yan Li
2008-06-06 6:46 ` Milan Broz [this message]
[not found] ` <2f83bcba0806031246m30f92892wc868d81a9c29d680@mail.gmail.com>
2008-06-03 23:13 ` Yan Li
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=4848DD3C.9000001@redhat.com \
--to=mbroz@redhat.com \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=christophe@saout.de \
--cc=dm-crypt@saout.de \
--cc=dm-devel@redhat.com \
--cc=elliot.li.tech@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rjmaomao@gmail.com \
--cc=rrs@researchut.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).