public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: Ulrich Lukas <stellplatz-nr.13a@datenparkplatz.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: Poor desktop responsiveness with background I/O-operations
Date: Sun, 20 Sep 2009 20:17:36 +0300	[thread overview]
Message-ID: <4AB663B0.9070600@arcor.de> (raw)
In-Reply-To: <4AB5ECD0.7010903@datenparkplatz.de>

(Please don't strip the CC list when you reply.  Use the "Reply to all" 
functionality of your mail client and keep all CCs.)

On 09/20/2009 11:50 AM, Ulrich Lukas wrote:
> Arjan van de Ven wrote:
>> can you try the following two things?
>>
>> echo 4096>  /sys/block/sda/queue/nr_requests
>> for i in `pidof kjournald` ; do ionice -c1 -p $i ; done
>
> I tried this just now, but it doesn't change things much. I can do a
> more testing later today.
>
>
>> I assume you're using CFQ.
>
> Yes, it's CFQ. (see .config of my previous posting)
>
> Filesystem is EXT4.

I can also confirm total lock-up when copying a big file (Intel Core 2 
Duo, Intel X38 chipset).  Everything locks-up for several seconds during 
the copying.  I'm also on ext4.  I've been told on various mailing lists 
that this is normal, expected and unavoidable so I pretty much think the 
only solution is to avoid heavy I/O :P

  reply	other threads:[~2009-09-20 17:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-20  3:08 Poor desktop responsiveness with background I/O-operations Ulrich Lukas
2009-09-20  4:11 ` Thomas Fjellstrom
2009-09-20  6:07 ` Arjan van de Ven
2009-09-20  8:50   ` Ulrich Lukas
2009-09-20 17:17     ` Nikos Chantziaras [this message]
2009-09-20 19:38     ` Mike Galbraith
2009-09-21  0:22       ` Justin P. Mattock
2009-09-21  4:23         ` Mike Galbraith
2009-09-21  7:48           ` Ulrich Lukas
2009-09-21  8:06             ` Mike Galbraith
2009-09-21 19:47               ` James Cloos
2009-09-21 22:47                 ` Nikos Chantziaras
2009-09-21 23:34                   ` James Cloos
2009-09-22  7:06                 ` Mike Galbraith
2009-09-22  9:20                   ` Mike Galbraith
2009-09-22 11:22                     ` Henrique de Moraes Holschuh
2009-09-22 11:32                       ` Mike Galbraith
2009-09-22 16:58                   ` James Cloos
2009-09-20 17:04   ` Ulrich Lukas
2009-09-20 20:22 ` Jiri Kosina
2009-09-20 22:04   ` Jan Kara
2009-09-21  7:25     ` Mike Galbraith
2009-09-21  7:33       ` Arjan van de Ven
2009-09-21  7:41         ` Mike Galbraith
2009-09-21  7:47           ` Mike Galbraith
2009-09-21  2:59   ` Ulrich Lukas
     [not found] <dmlhK-6ws-5@gated-at.bofh.it>
     [not found] ` <dmnMy-8tg-7@gated-at.bofh.it>
2009-09-20 18:51   ` Sanjoy Mahajan

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=4AB663B0.9070600@arcor.de \
    --to=realnc@arcor.de \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stellplatz-nr.13a@datenparkplatz.de \
    /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