From: Zan Lynx <zlynx@acm.org>
To: Prakash Punnoor <prakash@punnoor.de>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
Lukas Hejtmanek <xhejtman@ics.muni.cz>,
linux-kernel@vger.kernel.org
Subject: Re: Disk schedulers
Date: Fri, 15 Feb 2008 10:11:26 -0700 [thread overview]
Message-ID: <1203095486.6663.12.camel@localhost> (raw)
In-Reply-To: <200802151557.59082.prakash@punnoor.de>
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
On Fri, 2008-02-15 at 15:57 +0100, Prakash Punnoor wrote:
> On the day of Friday 15 February 2008 Jan Engelhardt hast written:
> > On Feb 14 2008 17:21, Lukas Hejtmanek wrote:
> > >Hello,
> > >
> > >whom should I blame about disk schedulers?
> >
> > Also consider
> > - DMA (e.g. only UDMA2 selected)
> > - aging disk
>
> Nope, I also reported this problem _years_ ago, but till now much hasn't
> changed. Large writes lead to read starvation.
Yes, I see this often myself. It's like the disk IO queue (I set mine
to 1024) fills up, and pdflush and friends can stuff write requests into
it much more quickly than any other programs can provide read requests.
CFQ and ionice work very well up until iostat shows average IO queuing
above 1024 (where I set the queue number).
--
Zan Lynx <zlynx@acm.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-02-15 17:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 16:21 Disk schedulers Lukas Hejtmanek
2008-02-15 0:02 ` Tejun Heo
2008-02-15 10:09 ` Lukas Hejtmanek
2008-02-15 14:42 ` Jan Engelhardt
2008-02-15 14:57 ` Prakash Punnoor
2008-02-15 17:11 ` Zan Lynx [this message]
2008-02-15 21:32 ` FD Cami
2008-02-16 16:13 ` Lukas Hejtmanek
2008-02-20 17:04 ` Zdenek Kabelac
2008-02-15 15:59 ` Lukas Hejtmanek
2008-02-15 16:22 ` Jeffrey E. Hundstad
2008-02-15 17:36 ` Roger Heflin
2008-02-15 17:24 ` Paulo Marques
2008-02-16 16:15 ` Lukas Hejtmanek
2008-02-16 17:20 ` Pavel Machek
2008-02-20 18:48 ` Lukas Hejtmanek
2008-02-21 23:50 ` Giuliano Pochini
2008-02-17 19:38 ` Linda Walsh
2008-02-28 17:14 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2011-02-04 12:30 Paresh Nakhe
2011-02-04 15:11 ` Pasi Kärkkäinen
2011-02-04 15:34 ` Paresh Nakhe
2011-02-04 15:51 ` Ian Campbell
2011-02-04 16:23 ` Paresh Nakhe
2011-02-04 16:28 ` Ian Campbell
2011-02-04 16:44 ` Paresh Nakhe
2011-02-04 17:30 ` Ian Campbell
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=1203095486.6663.12.camel@localhost \
--to=zlynx@acm.org \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=prakash@punnoor.de \
--cc=xhejtman@ics.muni.cz \
/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.