From: Herbert Xu <herbert@gondor.apana.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ritesh Raj Sarraf <rrs@researchut.com>,
Christophe Saout <christophe@saout.de>,
linux-kernel@vger.kernel.org, dm-devel@redhat.com
Subject: Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
Date: Sat, 1 Mar 2008 02:15:51 +0800 [thread overview]
Message-ID: <20080229181551.GA28193@gondor.apana.org.au> (raw)
In-Reply-To: <20080228232048.51e28c1d.akpm@linux-foundation.org>
On Thu, Feb 28, 2008 at 11:20:48PM -0800, Andrew Morton wrote:
>
> Now, I'm assuming that it's just unreasonable for a machine to spend a full
> 11 seconds crunching away on crypto in that code path. Maybe it _is_
> reasonable, and all we need to do is to poke a cond_resched() in there
> somewhere. Herbert, any thoughts? What's the speed of that code?
It encryps 512 bytes each time so it should definitely be pretty
quick. Perhaps the caller is disabling interrupts or something?
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2008-02-29 18:16 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 [this message]
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
[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=20080229181551.GA28193@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=akpm@linux-foundation.org \
--cc=christophe@saout.de \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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).