From: Evgeniy Ivanov <lolkaantimat@gmail.com>
To: Jesper Juhl <jj@chaosbits.net>
Cc: Dave Chinner <david@fromorbit.com>,
Chris Mason <chris.mason@oracle.com>, Ingo Molnar <mingo@elte.hu>,
Pekka Enberg <penberg@kernel.org>,
Aidar Kultayev <the.aidar@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jens Axboe <axboe@kernel.dk>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Nick Piggin <npiggin@suse.de>,
Arjan van de Ven <arjan@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>, Ted Ts'o <tytso@mit.edu>,
Corrado Zoccolo <czoccolo@gmail.com>,
Shaohua Li <shaohua.li@intel.com>,
Sanjoy Mahajan <sanjoy@olin.edu>,
Steven Barrett <damentz@gmail.com>
Subject: Re: 2.6.36 io bring the system to its knees
Date: Tue, 9 Nov 2010 22:47:38 +0300 [thread overview]
Message-ID: <AANLkTinZCBs_JO0Ug58uJdWEuqx=xzzBn2nJzdYr7+hb@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1011071753560.26056@swampdragon.chaosbits.net>
I have almost same problem (system is less interactive, but no freeze happens).
Here are tests I use (written by Alexander Nekrasov):
logrotate.sh (hard writer): http://pastebin.com/PPnSvP2f
writetest (small writer): http://pastebin.com/616JvWEK
If you run "writetest 15 realtime" timings will be OK, but if you also
run "logrotate.sh 300 3" you will see that RT processes start trashing
(timings periodically increase from 50ms to 2000-4000ms).
I do tests on 2.6.31, but same happens on 2.6.36. CFQ with default
settings is used. I've played with page-background.c and noticed, that
writeback still works for RT processes (no write through/disk wait). I
even tried to increase dirty_ratio for RT processes. Also I've limited
memory consumed by dd (logrotate.sh), since I had situation when it
consumed too much and kernel started to reclaim pages.
It doesn't want to work on ext3 (compiled and mounted like Linus
suggested in this thread), but works fine on ext4 with
"data=writeback" and on XFS. I'm not sure if it means that problem in
ext3 and in journaling (in case of ext4 without data=writeback).
I'm not sure if "data=writeback" (makes ext4 journaling similar to
XFS) really fixes the problem, probably it increases FS bandwidth, so
we just don't see the problem, but it can still present.
On Sun, Nov 7, 2010 at 8:16 PM, Jesper Juhl <jj@chaosbits.net> wrote:
> On Fri, 5 Nov 2010, Dave Chinner wrote:
>
>> On Fri, Nov 05, 2010 at 12:48:17AM +0100, Jesper Juhl wrote:
>> > On Fri, 5 Nov 2010, Jesper Juhl wrote:
>> >
>> > > On Thu, 28 Oct 2010, Chris Mason wrote:
>> > >
>> > > > On Thu, Oct 28, 2010 at 03:30:36PM +0200, Ingo Molnar wrote:
>> > > > >
>> > > > > "Many seconds freezes" and slowdowns wont be fixed via the VFS scalability patches
>> > > > > i'm afraid.
>> > > > >
>> > > > > This has the appearance of some really bad IO or VM latency problem. Unfixed and
>> > > > > present in stable kernel versions going from years ago all the way to v2.6.36.
>> > > >
>> > > > Hmmm, the workload you're describing here has two special parts. First
>> > > > it dramatically overloads the disk, and then it has guis doing things
>> > > > waiting for the disk.
>> > > >
>> > >
>> > > Just want to chime in with a 'me too'.
>> > >
>> > > I see something similar on Arch Linux when doing 'pacman -Syyuv' and there
>> > > are many (as in more than 5-10) updates to apply. While the update is
>> > > running (even if that's all the system is doing) system responsiveness is
>> > > terrible - just starting 'chromium' which is usually instant (at least
>> > > less than 2 sec at worst) can take upwards of 10 seconds and the mouse
>> > > cursor in X starts to jump a bit as well and switching virtual desktops
>> > > noticably lags when redrawing the new desktop if there's a full screen app
>> > > like gimp or OpenOffice open there. This is on a Lenovo Thinkpad R61i
>> > > which has a 'Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz' CPU, 2GB of
>> > > memory and 499996 kilobytes of swap.
>> > >
>> > Forgot to mention the kernel I currently experience this with :
>> >
>> > [jj@dragon ~]$ uname -a
>> > Linux dragon 2.6.35-ARCH #1 SMP PREEMPT Sat Oct 30 21:22:26 CEST 2010 x86_64 Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz GenuineIntel GNU/Linux
>>
>> I think anyone reporting a interactivity problem also needs to
>> indicate what their filesystem is, what mount paramters they are
>> using, what their storage config is, whether barriers are active or
>> not, what elevator they are using, whether one or more of the
>> applications are issuing fsync() or sync() calls, and so on.
>>
> Some details below.
>
> [jj@dragon ~]$ mount
> proc on /proc type proc (rw,relatime)
> sys on /sys type sysfs (rw,relatime)
> udev on /dev type devtmpfs
> (rw,nosuid,relatime,size=10240k,nr_inodes=255749,mode=755)
> /dev/disk/by-uuid/61d104a5-4f7b-40ef-a9c8-44ad2765513e on / type ext4 (rw,commit=0)
> devpts on /dev/pts type devpts (rw)
> shm on /dev/shm type tmpfs (rw,nosuid,nodev)
>
> [root@dragon ~]# hdparm -v /dev/disk/by-uuid/61d104a5-4f7b-40ef-a9c8-44ad2765513e
>
> /dev/disk/by-uuid/61d104a5-4f7b-40ef-a9c8-44ad2765513e:
> multcount = 16 (on)
> IO_support = 1 (32-bit)
> readonly = 0 (off)
> readahead = 256 (on)
> geometry = 9729/255/63, sectors = 25220160, start = 119644560
>
> [root@dragon ~]# dmesg | grep -i ext4
> EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
> EXT4-fs (sda4): re-mounted. Opts: (null)
> EXT4-fs (sda4): re-mounted. Opts: (null)
> EXT4-fs (sda4): re-mounted. Opts: commit=0
>
> The elevator in use is CFQ.
>
> The app that's causing the system to behave this way (the 'pacman' package
> manager in Arch Linux) makes a few calls (2-4) to fsync() during its run,
> but that's all.
>
>
> --
> Jesper Juhl <jj@chaosbits.net> http://www.chaosbits.net/
> Plain text mails only, please http://www.expita.com/nomime.html
> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>
--
Evgeniy Ivanov
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-11-09 19:53 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimt7wzR9RwGWbvhiOmot_zzayfCfSh_-v6yvuAP@mail.gmail.com>
[not found] ` <AANLkTikRKVBzO=ruy=JDmBF28NiUdJmAqb4-1VhK0QBX@mail.gmail.com>
[not found] ` <AANLkTinzJ9a+9w7G5X0uZpX2o-L8E6XW98VFKoF1R_-S@mail.gmail.com>
2010-10-28 6:09 ` Aidar Kultayev
2010-10-28 6:32 ` Pekka Enberg
2010-10-28 9:00 ` Ingo Molnar
2010-10-28 9:34 ` Pekka Enberg
2010-10-28 11:16 ` Pekka Enberg
2010-10-28 11:33 ` Aidar Kultayev
2010-10-28 11:48 ` Pekka Enberg
2010-10-28 12:18 ` Aidar Kultayev
2010-10-28 13:46 ` Christoph Hellwig
2010-10-28 13:54 ` Ingo Molnar
2010-10-28 13:30 ` Ingo Molnar
2010-10-28 13:47 ` Christoph Hellwig
2010-10-28 13:50 ` Ingo Molnar
2010-10-28 17:01 ` Chris Mason
2010-10-28 17:57 ` Pekka Enberg
2010-10-29 14:52 ` Ted Ts'o
2010-10-29 15:33 ` Aidar Kultayev
2010-10-30 9:14 ` Ingo Molnar
2010-10-30 13:02 ` Aidar Kultayev
2010-10-30 19:06 ` Chris Mason
2010-10-31 2:31 ` Ted Ts'o
2010-10-31 17:49 ` Corrado Zoccolo
2010-11-02 3:10 ` Shaohua Li
2010-11-02 11:47 ` Sanjoy Mahajan
2010-11-02 13:12 ` Chris Mason
2010-11-04 16:05 ` Sanjoy Mahajan
2010-11-04 23:35 ` Steven Barrett
2010-11-04 23:44 ` Jesper Juhl
2010-11-04 23:48 ` Jesper Juhl
2010-11-05 1:43 ` Dave Chinner
2010-11-05 12:48 ` Sanjoy Mahajan
2010-11-06 14:10 ` dave b
2010-11-06 15:12 ` Dave Chinner
2010-11-07 6:06 ` dave b
2010-11-07 12:08 ` Jens Axboe
2010-11-07 15:50 ` Linus Torvalds
2010-11-10 1:32 ` Dave Chinner
2010-11-10 2:01 ` dave b
2010-11-10 8:08 ` Evgeniy Ivanov
2010-11-10 8:24 ` Dave Chinner
2010-11-10 14:22 ` Pavel Machek
2010-11-10 14:20 ` Pavel Machek
2010-11-10 14:27 ` Ingo Molnar
2010-11-10 14:55 ` Christoph Hellwig
2010-11-10 19:09 ` Pavel Machek
2010-11-10 14:33 ` Theodore Tso
2010-11-10 14:57 ` Christoph Hellwig
2010-11-10 15:00 ` Chris Mason
2010-11-10 23:36 ` Dave Chinner
2010-11-10 15:59 ` Linus Torvalds
2010-11-10 16:46 ` Alexey Dobriyan
2010-11-10 16:55 ` Linus Torvalds
2010-11-10 17:10 ` Alexey Dobriyan
2010-11-10 18:55 ` Mark Lord
2010-11-10 18:27 ` Mike Galbraith
2010-11-10 23:43 ` Dave Chinner
2010-11-06 19:10 ` Arjan van de Ven
2010-11-07 17:16 ` Jesper Juhl
2010-11-09 19:47 ` Evgeniy Ivanov [this message]
2010-11-09 20:20 ` Christoph Hellwig
2010-11-09 21:00 ` Chris Mason
2010-10-31 1:22 ` Wu Fengguang
2010-10-31 1:51 ` Wu Fengguang
2010-11-01 1:09 ` Dimitrios Apostolou
2010-11-02 1:20 ` Wu Fengguang
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='AANLkTinZCBs_JO0Ug58uJdWEuqx=xzzBn2nJzdYr7+hb@mail.gmail.com' \
--to=lolkaantimat@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=axboe@kernel.dk \
--cc=chris.mason@oracle.com \
--cc=czoccolo@gmail.com \
--cc=damentz@gmail.com \
--cc=david@fromorbit.com \
--cc=jj@chaosbits.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=penberg@kernel.org \
--cc=sanjoy@olin.edu \
--cc=shaohua.li@intel.com \
--cc=tglx@linutronix.de \
--cc=the.aidar@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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