From: Zan Lynx <zlynx@acm.org>
To: ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>
Subject: Interesting observation on Reiser4 flush delays and IO scheduler
Date: Thu, 02 Aug 2007 14:28:28 -0600 [thread overview]
Message-ID: <1186086508.14479.14.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
On my laptop while running heavy disk read/write loads, I have
discovered that the deadline IO scheduler gives me a much better "feel"
and much shorter (and fewer) system freezes. This is as compared to the
CFQ scheduler.
I'm not sure why this is yet. A rough guess is that Reiser4's atom
merging, etc, is not preserving the data CFQ needs to time slice and
prioritize disk IO. But I don't have any evidence for this guess. Is
it plausible?
Something to think about.
--
Zan Lynx <zlynx@acm.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-08-02 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 20:28 Zan Lynx [this message]
2007-08-07 17:40 ` Interesting observation on Reiser4 flush delays and IO scheduler Zan Lynx
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=1186086508.14479.14.camel@localhost \
--to=zlynx@acm.org \
--cc=reiserfs-devel@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.