From: Aidar Kultayev <the.aidar@gmail.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
npiggin@kernel.dk, Dave Chinner <david@fromorbit.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 2.6.36 io bring the system to its knees
Date: Thu, 28 Oct 2010 18:18:05 +0600 [thread overview]
Message-ID: <AANLkTi=Yt-vK-=8X8xu0htCQeEieEGfkWMCRYKUeK+PF@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikx4zZwMLiAUrGKcH6yoo_PGgRA7nT9BzYMxQ89@mail.gmail.com>
http://picasaweb.google.com/aidar.eiei/LinuxIo#5533068249408411698
I will look into latencytop output and will figure out a usage pattern
that is most annoying with regards to IO.
Will try to see what leads to that & if possible to make a screenshot
of what is going on.
The thing is, I don't think the program that captures the screenshots
does it in a meaningful way, because at the moment the system is
brought to its knees, I don't think that this particular program
(KSnapshot) can get away from being affected. I mean it might take a
snapshot which is not representative enough.
thanks, Aidar
On Thu, Oct 28, 2010 at 5:48 PM, Pekka Enberg <penberg@kernel.org> wrote:
> On Thu, Oct 28, 2010 at 2:33 PM, Aidar Kultayev <the.aidar@gmail.com> wrote:
>> if it wasn't picasa, it would have been something else. I mean if I
>> kill picasa ( later on it was done indexing new pics anyway ), it
>> would have been for virtualbox to thrash the io. So, nope, getting rid
>> of picasa doesn't help either. In general the systems responsiveness
>> or sluggishness is dominated by those io operations going on - the DD
>> & CP & probably VBOX issuing whole bunch of its load for IO.
>
> Do you still see high latencies in vfs_lseek() and vfs_fsync()? I'm
> not a VFS expert but looking at your latencytop output, it seems that
> fsync grabs ->i_mutex which blocks vfs_llseek(), for example. I'm not
> sure why that causes high latencies though it's a mutex we're holding.
>
> On Thu, Oct 28, 2010 at 2:33 PM, Aidar Kultayev <the.aidar@gmail.com> wrote:
>> Another way I see these delays, is when I leave system overnight, with
>> ktorrent & juk(stopped) in the background. It takes some time for
>> WM(kwin) to work out ALT+TAB the very next morning. But this might be
>> because the WM(kwin & its code) has been swapped out, because of long
>> period of not using it.
>
> Yeah, that's probably paging overhead.
>
> P.S. Can you please upload latencytop output somewhere and post an URL
> to it so other people can also see it?
>
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-10-28 12:18 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 [this message]
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
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='AANLkTi=Yt-vK-=8X8xu0htCQeEieEGfkWMCRYKUeK+PF@mail.gmail.com' \
--to=the.aidar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=npiggin@kernel.dk \
--cc=penberg@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