From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 14830] When other IO is running sync times go to 10 to 20 minutes
Date: Thu, 20 May 2010 02:11:55 GMT [thread overview]
Message-ID: <201005200211.o4K2BtG0030354@demeter.kernel.org> (raw)
In-Reply-To: <bug-14830-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=14830
Justin Maggard <jmaggard10@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jmaggard10@gmail.com
--- Comment #39 from Justin Maggard <jmaggard10@gmail.com> 2010-05-20 02:11:11 ---
(In reply to comment #28)
> Created an attachment (id=25883)
--> (https://bugzilla.kernel.org/attachment.cgi?id=25883) [details]
> Patch to stop background writeback when other work is queued for the thread
>
> Oops, attached a wrong patch. This is the right one.
I ran into this issue recently (extra long sync times) and have been trying the
patches attached in this thread. The above patch specifically causes a pretty
significant performance regression for me doing a simple sequential dd write on
a dual-core Atom system running 2.6.33.4 x86_64. This command:
dd bs=1M conv=fsync if=/dev/zero of=test_file count=10000
went from 135 MB/sec to all the way down to 92.9 MB/sec. Is this expected?
--
Configure bugmail: https://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-05-20 2:11 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14830-13602@https.bugzilla.kernel.org/>
2010-04-02 5:41 ` [Bug 14830] When other IO is running sync times go to 10 to 20 minutes bugzilla-daemon
2010-04-02 21:23 ` bugzilla-daemon
2010-04-06 16:47 ` bugzilla-daemon
2010-04-06 16:49 ` bugzilla-daemon
2010-04-06 16:50 ` bugzilla-daemon
2010-04-06 16:52 ` bugzilla-daemon
2010-04-06 16:55 ` bugzilla-daemon
2010-04-06 23:01 ` bugzilla-daemon
2010-04-06 23:06 ` bugzilla-daemon
2010-04-07 9:33 ` bugzilla-daemon
2010-04-07 15:10 ` bugzilla-daemon
2010-04-15 8:45 ` bugzilla-daemon
2010-04-20 2:49 ` bugzilla-daemon
2010-04-20 3:46 ` bugzilla-daemon
2010-04-29 9:31 ` bugzilla-daemon
2010-04-30 6:02 ` bugzilla-daemon
2010-05-20 2:11 ` bugzilla-daemon [this message]
2010-05-20 11:11 ` bugzilla-daemon
2010-05-20 17:53 ` bugzilla-daemon
2012-06-18 13:19 ` bugzilla-daemon
2012-06-18 13:19 ` bugzilla-daemon
[not found] <bug-14830-13602@http.bugzilla.kernel.org/>
2010-01-13 19:15 ` bugzilla-daemon
2010-01-18 21:50 ` bugzilla-daemon
2010-01-18 23:58 ` bugzilla-daemon
2010-01-19 17:24 ` Chris Lee
2010-01-19 17:24 ` bugzilla-daemon
2010-01-19 19:38 ` bugzilla-daemon
2010-01-19 21:56 ` bugzilla-daemon
2010-01-25 7:38 ` bugzilla-daemon
2010-01-25 8:27 ` bugzilla-daemon
2010-01-25 11:07 ` bugzilla-daemon
2010-01-25 11:16 ` bugzilla-daemon
2010-01-25 11:19 ` bugzilla-daemon
2010-01-27 13:06 ` Andre Noll
2010-01-27 19:43 ` Andreas Dilger
2010-01-28 10:24 ` Andre Noll
2010-01-28 7:53 ` tytso
2010-01-28 10:25 ` Andre Noll
2010-01-28 9:18 ` bugzilla-daemon
2010-01-28 11:23 ` bugzilla-daemon
2010-01-28 16:22 ` bugzilla-daemon
2010-01-29 0:52 ` bugzilla-daemon
2010-01-29 6:37 ` bugzilla-daemon
2010-02-04 4:16 ` bugzilla-daemon
2010-02-15 14:28 ` bugzilla-daemon
2010-02-15 18:29 ` bugzilla-daemon
2010-03-10 6:56 ` bugzilla-daemon
2010-03-10 15:36 ` 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=201005200211.o4K2BtG0030354@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.