From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 14972] [regression] msync() call on ext4 causes disk thrashing
Date: Sat, 2 Jan 2010 17:54:55 GMT [thread overview]
Message-ID: <201001021754.o02HstpS022786@demeter.kernel.org> (raw)
In-Reply-To: <bug-14972-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=14972
--- Comment #6 from Theodore Tso <tytso@mit.edu> 2010-01-02 17:54:54 ---
You need to compile kernel with CONFIG_BLK_DEV_IO_TRACE and then you need to
make sure that the debugfs file system is mounted in /sys/kernel/debug, i.e.:
mount -t debugfs none /sys/kernel/debug
The following documentation is from 2007, so there are some newer features (and
the underlying implementation has moved to using ftrace), but the basic user
interface hasn't changed much:
http://pdfedit.petricek.net/bt/file_download.php?file_id=17&type=bug
More information:
http://www.gelato.org/pdf/apr2006/gelato_ICE06apr_blktrace_brunelle_hp.pdf
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2010-01-02 17:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 23:09 [Bug 14972] New: [regression] msync() call on ext4 causes disk thrashing bugzilla-daemon
2010-01-01 23:14 ` [Bug 14972] " bugzilla-daemon
2010-01-02 13:19 ` bugzilla-daemon
2010-01-02 15:10 ` bugzilla-daemon
2010-01-02 16:47 ` bugzilla-daemon
2010-01-02 16:48 ` bugzilla-daemon
2010-01-02 16:54 ` bugzilla-daemon
2010-01-02 17:54 ` bugzilla-daemon [this message]
2010-01-03 10:31 ` bugzilla-daemon
2010-01-03 12:11 ` bugzilla-daemon
2010-01-03 12:38 ` bugzilla-daemon
2010-01-04 3:35 ` bugzilla-daemon
2010-01-04 10:05 ` bugzilla-daemon
[not found] <bug-14972-13602@https.bugzilla.kernel.org/>
2011-03-03 11:25 ` bugzilla-daemon
2012-01-11 0:08 ` bugzilla-daemon
2012-03-17 8:46 ` bugzilla-daemon
2012-03-17 9:07 ` bugzilla-daemon
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=201001021754.o02HstpS022786@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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.