linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] O13.1int
Date: Tue, 05 Aug 2003 09:31:07 +0200	[thread overview]
Message-ID: <1060068667.556.1.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <200308051017.55616.kernel@kolivas.org>

On Tue, 2003-08-05 at 02:17, Con Kolivas wrote:
> A heck of a lot fairer on disk only tasks; lets them earn sleep avg up to just 
> interactive state so they stay on the active array.

This one is more "jumpy" (i.e., not as smooth as) than just the previous
release. I have had to renice X back to -20 in order to get smooth
window movements involving heavyweight CPU programs like Evolution.

Also, with X at -20, XMMS skips are still present, but they are a little
bit shorter than with previous iterations.


      reply	other threads:[~2003-08-05  7:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05  0:17 [PATCH] O13.1int Con Kolivas
2003-08-05  7:31 ` Felipe Alfaro Solana [this message]

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=1060068667.556.1.camel@teapot.felipe-alfaro.com \
    --to=felipe_alfaro@linuxmail.org \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.org \
    --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;
as well as URLs for NNTP newsgroup(s).