From: Nikos Chantziaras <realnc@arcor.de>
To: James Cloos <cloos@jhcloos.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Ulrich Lukas <stellplatz-nr.13a@datenparkplatz.de>,
Mike Galbraith <efault@gmx.de>
Subject: Re: Poor desktop responsiveness with background I/O-operations
Date: Tue, 22 Sep 2009 01:47:22 +0300 [thread overview]
Message-ID: <4AB8027A.1040600@arcor.de> (raw)
In-Reply-To: <m3tyyw6pvz.fsf@lugabout.jhcloos.org>
On 09/21/2009 10:47 PM, James Cloos wrote:
>[...]
> I had that kernel up for soemthing like five weeks, on a busy, low-ram
> laptop, w/o and long pauses or other noticeable pain. For at least two
> years before that the best this laptop could manage before latency
> became horrific was a fortnight, and weekly reboots were desirable.
>
> Unfortunately, before I could send out a congratulatory note (I wanted
> to first confirm that the result remained) I pulled up and started see-
> ing even worse latency then ever.
>[...]
> A git pull on a clone of Linus' tree is a great way to trigger the
> problem. As is using Gentoo's portage to install/upgrade anything.
> (Bad python; no alligator!¹)
Fortunately, this is completely (at least here) solved by putting those
in make.conf:
PORTAGE_NICENESS=19
PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}"
next prev parent reply other threads:[~2009-09-21 22:47 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 [this message]
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=4AB8027A.1040600@arcor.de \
--to=realnc@arcor.de \
--cc=cloos@jhcloos.com \
--cc=efault@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.