From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 14972] New: [regression] msync() call on ext4 causes disk thrashing
Date: Fri, 1 Jan 2010 23:09:50 GMT [thread overview]
Message-ID: <bug-14972-13602@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=14972
Summary: [regression] msync() call on ext4 causes disk
thrashing
Product: File System
Version: 2.5
Kernel Version: 2.6.32.2
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: t.artem@mailcity.com
Regression: Yes
Created an attachment (id=24398)
--> (http://bugzilla.kernel.org/attachment.cgi?id=24398)
run this way ./test test.txt 100
The attached application causes useless disk thrashing in case of ext4, but
works normally in case of ext3 (and possibly other FS's).
msync() for unchanged mmap'ed files shouldn't cause disk/HDD activity which I
do observe.
--
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 reply other threads:[~2010-01-01 23:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 23:09 bugzilla-daemon [this message]
2010-01-01 23:14 ` [Bug 14972] [regression] msync() call on ext4 causes disk thrashing 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
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
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=bug-14972-13602@http.bugzilla.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 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).