From: Andrew Morton <akpm@osdl.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-...: looong writeouts
Date: Wed, 28 Jun 2006 20:55:39 -0700 [thread overview]
Message-ID: <20060628205539.f7e1c43b.akpm@osdl.org> (raw)
In-Reply-To: <20060624151531.GA7565@martell.zuzino.mipt.ru>
On Sat, 24 Jun 2006 19:15:31 +0400
Alexey Dobriyan <adobriyan@gmail.com> wrote:
> Immediate problem: from time to time post 2.6.17 kernel [1] decides that it
> really really needs disk.
>
> [kernel compilation goes as usual]
> CC [M] fs/xfs/xfs_inode.o
> [compilation blocks for ~10 seconds, disk LED is red]
> [then it continues]
>
> Again, from time to time saving 2k file makes vi inoperational for same
> period.
>
> Scheduler is CFQ, fs is reiserfs mounted with noatime, notail. 2.6.17-rc
> and 2.6.17 kernels were OK.
>
> It occured only several times in 4 hours.
>
> [1] 2.6.17-95eaa5fa8eb2c345244acd5f65b200b115ae8c65 to be precise
>
>
> Probably related problem below:
>
> During 2.6.17-rc cycle CFQ subjectively became less F.
>
> [ unpacking ]
> [kernel tarball]
> .
> .
> .
> .
> .
> .
> . [:wq on little file]
> .
> .
> .
> .
> .
> .
> [ ]
>
> IIRC, on 2.6.16 that :wq took say 0.5 sec, on late 2.6.17-rc it was
> several times slower. I don't have numbers but it was psychologically
> noticeable, but not BFD.
>
There have been quite a few CFQ changes.
It'd help if you can come up with a simple test case which others can use
to reproduce this. Say,
while true
do
dd if=/dev/zero of=foo bs-1M count=1000 conv=notrunc
done &
versus
time dd if=/dev/zero of=bar bs=16k count=1 conv=fsync
or something like that.
Thanks.
next prev parent reply other threads:[~2006-06-29 3:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 15:15 Alexey Dobriyan
2006-06-29 3:55 ` Andrew Morton [this message]
2006-06-24 16:30 Donald Parsons
2006-06-24 16:50 ` Arjan van de Ven
2006-06-24 17:36 ` Alexey Dobriyan
2006-06-24 17:41 ` Arjan van de Ven
2006-06-25 0:11 ` Donald Parsons
2006-06-25 2:33 ` Donald Parsons
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=20060628205539.f7e1c43b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adobriyan@gmail.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 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®