[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120517211825.DD9BC11FCF6@bugzilla.kernel.org>
Date: Thu, 17 May 2012 21:18:25 +0000 (UTC)
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 42895] jbd2 makes all system unresponsive
https://bugzilla.kernel.org/show_bug.cgi?id=42895
Sami Liedes <sliedes@...hut.fi> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sliedes@...hut.fi
--- Comment #19 from Sami Liedes <sliedes@...hut.fi> 2012-05-17 21:18:25 ---
I have seen this too; basically latencies have always been a problem with KDE
(at least KDE 4) on ext4, as far as I can tell. Switching to XFS solved the
problem for me.
One thing I might be able to add to the discussion:
While this problem manifests without disk crypto, adding dm-crypt to the soup,
especially on a computer _without_ hardware AES support, generally makes it
*much* worse. I've seen disk accesses, especially fsync()s (per latencytop),
take minutes in the worst case under some medium disk load; 5-10 seconds are a
norm on light I/O load. I can't see much reason why disk crypto should make it
that much slower. But since it's a problem also without crypto, perhaps
dm-crypt just somehow makes it worse and more obvious?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists