From: Lee Revell <rlrevell@joe-job.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Christian <christiand59@web.de>, linux-kernel@vger.kernel.org
Subject: Re: Sluggish system responsiveness on I/O
Date: Sun, 19 Nov 2006 12:44:47 -0500 [thread overview]
Message-ID: <1163958288.22176.82.camel@mindpipe> (raw)
In-Reply-To: <1163922694.7504.42.camel@Homer.simpson.net>
On Sun, 2006-11-19 at 08:51 +0100, Mike Galbraith wrote:
> That makes sense, I/O tasks don't generally hold the cpu for extended
> periods, whereas a cpu bound task does.
So what can we do about I/O intensive tasks that also want a lot of CPU,
for example, the bloatier Gnome/KDE apps? Evolution is the worst for
me.
Lee
next prev parent reply other threads:[~2006-11-19 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 13:12 Sluggish system responsiveness on I/O Christian
2006-11-18 13:25 ` Prakash Punnoor
2006-11-18 14:40 ` Christian
2006-11-19 7:51 ` Mike Galbraith
2006-11-19 17:44 ` Lee Revell [this message]
2006-11-19 18:34 ` Mike Galbraith
2006-11-22 10:57 ` [rfc patch] " Mike Galbraith
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=1163958288.22176.82.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=christiand59@web.de \
--cc=efault@gmx.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 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.