From: <spaminos-ker@yahoo.com>
To: Jens Axboe <axboe@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: cfq misbehaving on 2.6.11-1.14_FC3
Date: Wed, 22 Jun 2005 10:54:57 -0700 (PDT) [thread overview]
Message-ID: <20050622175457.18548.qmail@web30712.mail.mud.yahoo.com> (raw)
In-Reply-To: <1119432285.3257.5.camel@linux>
--- Jens Axboe <axboe@suse.de> wrote:
> THe problem here is that cfq (and the other io schedulers) still
> consider the io async even if fsync() ends up waiting for it to
> complete. So there's no real QOS being applied to these pending writes,
> and I don't immediately see how we can improve that situation right now.
<I might sound stupid>
I still don't understand why async requests are in a different queue than the
sync ones?
Wouldn't it be simpler to consider all the IO the same, and like you pointed
out, consider synced IO to be equivalent to async + some sync (as in wait for
completion) call (fsync goes a little too far).
</I might sound stupid>
>
> What file system are you using? I ran your test on ext2, and it didn't
> give me more than ~2 seconds latency for the fsync. Tried reiserfs now,
> and it's in the 23-24 range.
>
I am using ext3 on Fedora Core 3.
next prev parent reply other threads:[~2005-06-22 18:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 22:54 spaminos-ker
2005-06-11 9:29 ` Andrew Morton
2005-06-14 2:19 ` spaminos-ker
2005-06-14 7:03 ` Andrew Morton
2005-06-14 23:21 ` spaminos-ker
2005-06-17 14:10 ` Jens Axboe
2005-06-17 15:51 ` Andrea Arcangeli
2005-06-17 18:16 ` Jens Axboe
2005-06-17 23:01 ` spaminos-ker
2005-06-22 9:24 ` Jens Axboe
2005-06-22 17:54 ` spaminos-ker [this message]
2005-06-22 20:43 ` Jens Axboe
2005-06-23 18:30 ` spaminos-ker
2005-06-23 23:33 ` Con Kolivas
2005-06-24 2:33 ` spaminos-ker
2005-06-24 3:27 ` Con Kolivas
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=20050622175457.18548.qmail@web30712.mail.mud.yahoo.com \
--to=spaminos-ker@yahoo.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®