From: Zoltan NAGY <nagyz@nefty.hu>
To: linux-kernel@vger.kernel.org
Subject: pdflush and dm-crypt
Date: Mon, 29 Mar 2004 16:50:02 +0200 [thread overview]
Message-ID: <1067885681.20040329165002@nefty.hu> (raw)
Hi!
I've just upgraded the system to 2.6.5-rc2-bk6, and I'm using
dm-crypt. It's a heavily used server, on average 20-30mbit/sec
traffic is on the wire 7/24, and just noticed, that the load is very
high. In every 4-5 sec pdflush takes a lot of cpu... Is this
intentional? I've found a similar question on kerneltrap
(http://kerneltrap.org/node/view/2756), but havent found a solution
yet. I'm just wondering if it is a problem, or it's the normal
behavior? It's a 1.8 P4 with 1G ram and highmem enabled, with 256 bit
aes thru dm-crypt.
Regards,
--
Zoltan NAGY,
Network Administrator
next reply other threads:[~2004-03-29 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 14:50 Zoltan NAGY [this message]
2004-03-29 15:01 ` pdflush and dm-crypt Jens Axboe
2004-03-30 0:12 ` Andrew Morton
2004-03-30 6:22 ` Jens Axboe
2004-03-30 9:46 ` Christophe Saout
2004-03-30 10:07 ` Andrew Morton
2004-03-30 11:59 ` Zoltan NAGY
2004-03-29 15:01 ` Arkadiusz Miskiewicz
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=1067885681.20040329165002@nefty.hu \
--to=nagyz@nefty.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox