From: Sebastian Kuzminsky <seb@highlab.com>
To: linux-kernel@vger.kernel.org, seb@highlab.com
Subject: io priorities?
Date: Thu, 01 Jul 2004 12:14:05 -0600 [thread overview]
Message-ID: <E1Bg64T-0003MC-00@highlab.com> (raw)
Hi folks, i've got IO problems...
I've got a computer with one IDE disk. There are a couple of processes
writing big telemetry logs, totally not time-critical. Then there's one
process periodically writing a tiny little state file, about 150 bytes.
The process with the state file wants to sync its file to disk and then
quickly be back and running. When it calls fsync() it has to wait for
other processes' less-important pending I/O before it gets to complete,
and it's not unusual for this to take 30 seconds (CF over IDE), which
is too slow for my application.
This happens with both 2.4.23 and 2.6.6 (as, cfq, & deadline). I havent
tried to tune the schedulers at all, just using the default values.
I've tried five methods of syncing the file: sync(), fsync(), fdatasync(),
and opening with O_SYNC or O_DSYNC. All take about the same amount
of time.
I've tried it on my target machine (Compact Flash via pio IDE) and on
my development machine (regular hard drive via udma5 IDE). Same results
qualitatively speaking.
I read Jens Axboe's thread about cfq + io priorities, and it sounds
perfect! I could give my one time-critical process high io priority
and it should preempt the others and life would be fine. But all the
l-k traffic i've found about this is from back in November. Did this
work go anywhere?
Any suggestions on fixes or workarounds?
I'm stumped.
--
Sebastian
next reply other threads:[~2004-07-01 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 18:14 Sebastian Kuzminsky [this message]
2004-07-01 19:07 ` io priorities? Richard B. Johnson
2004-07-01 22:56 ` Andrew Morton
2004-07-01 23:15 ` Sebastian Kuzminsky
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=E1Bg64T-0003MC-00@highlab.com \
--to=seb@highlab.com \
--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 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.