mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Con Kolivas <kernel@kolivas.org>
Cc: Zwane Mwaikambo <zwane@linuxpower.ca>,
	Andreas Boman <aboman@midgaard.us>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Mike Galbraith <efault@gmx.de>
Subject: Re: [PATCH] sleep_decay for interactivity 2.5.72 - testers  needed
Date: 23 Jun 2003 13:16:15 +0200	[thread overview]
Message-ID: <1056366975.587.2.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <200306230737.17766.kernel@kolivas.org>

On Sun, 2003-06-22 at 23:37, Con Kolivas wrote:
> > > > Yes Mike's patches are definitely better. My patches are designed for
> > > > the 2.4-ck patchset which has other workarounds that augment this
> > > > patch; however these workarounds are harder to stomach for mainstream
> > > > kernels (read nasty hacks). I thought I'd offer the not so nasty
> > > > sleep_decay patch in 2.5 form for perusal and comments since people are
> > > > more willing to test 2.5 patches.
> > >
> > > Well, it's nice to know.
> > > I'm willing to test nearly any 2.5 patch. So, I'll gladly test any other
> > > ideas or patches you (or others) might have.
> >
> > ANY?
> >
> > Ok well I guess I have to give away my secret then. This is the change that
> > turns 2.5 into a desktop kernel. Note the very slight change to Ingo's
> > addon ;-)

OK, I've tested this patch but I still can easily make XMMS starve for
briefs periods of time and can also make X to start behaving jerky. If I
put the system under load (while true; do a=2; done) dragging a window
fast enough for a long time makes the X server priority decreases to a
point where the window moving is not smooth and very jerky. If I stop
dragging the window, after a while, the X server prority is restablished
and I can start all over again.


  reply	other threads:[~2003-06-23 11:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-19 14:05 Con Kolivas
2003-06-19 15:47 ` Mike Galbraith
2003-06-19 15:51   ` Con Kolivas
2003-06-19 16:02   ` Con Kolivas
2003-06-19 16:06     ` Con Kolivas
2003-06-19 16:42       ` Andreas Boman
2003-06-19 16:50         ` Con Kolivas
     [not found]           ` <1056058342.917.69.camel@asgaard.midgaard.us>
2003-06-20  2:29             ` Con Kolivas
2003-06-20 11:09               ` Mike Galbraith
2003-06-22 13:35               ` Con Kolivas
2003-06-22 13:45                 ` Con Kolivas
2003-06-22 15:40                   ` Felipe Alfaro Solana
2003-06-22 15:58                     ` Con Kolivas
2003-06-22 16:14                       ` Felipe Alfaro Solana
2003-06-22 21:24                         ` Con Kolivas
2003-06-22 21:37                           ` Con Kolivas
2003-06-23 11:16                             ` Felipe Alfaro Solana [this message]
2003-06-23 11:21                               ` Con Kolivas
2003-06-19 17:31     ` Mike Galbraith
2003-06-19 18:51       ` Andreas Boman

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=1056366975.587.2.camel@teapot.felipe-alfaro.com \
    --to=felipe_alfaro@linuxmail.org \
    --cc=aboman@midgaard.us \
    --cc=efault@gmx.de \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /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

all inboxes | Powered by JetHome®