From: Ulrich Lukas <stellplatz-nr.13a@datenparkplatz.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Poor desktop responsiveness with background I/O-operations
Date: Mon, 21 Sep 2009 04:59:21 +0200 [thread overview]
Message-ID: <4AB6EC09.9010808@datenparkplatz.de> (raw)
In-Reply-To: <alpine.LRH.2.00.0909202221010.25928@twin.jikos.cz>
Jiri Kosina wrote:
> I guess that switching from CFQ to deadline I/O scheduler improves the
> situation, right?
Indeed, there is an improvement. But, especially in the case with an
encrypted /home, copying a large file from a fast source means I better
go get another cup of coffee rather than continue working on something
else in the meantime.
BTW, I've tested this with a default install of
OpenSUSE 11.1, and I get basically the same behaviour.
next prev parent reply other threads:[~2009-09-21 2:59 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
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 [this message]
[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=4AB6EC09.9010808@datenparkplatz.de \
--to=stellplatz-nr.13a@datenparkplatz.de \
--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