mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mike Galbraith <efault@gmx.de>, Andrew Morton <akpm@digeo.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	Robert Love <rml@tech9.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] "interactivity changes", sched-2.5.64-B2
Date: 07 Mar 2003 22:05:57 +0100	[thread overview]
Message-ID: <1047071156.29990.5.camel@tux.rsn.bth.se> (raw)
In-Reply-To: <Pine.LNX.4.44.0303072136590.22681-100000@localhost.localdomain>

On Fri, 2003-03-07 at 21:39, Ingo Molnar wrote:
> On 7 Mar 2003, Martin Josefsson wrote:
> 
> > Some negative things:
> 
> if you have time/interest, could you re-test the negative things with X
> reniced to -10, to further isolate the problem? Another thing to try is to
> renice xmms to -10 (or RT priority). Which one makes the larger
> difference?

X niced to -10 makes the xmms mouse-jerkyness disappear. but it can
still skip right after a songchange. If I renice xmms to -10 as well I
get the mouse-jerkyness again, it I renice it to -5 it seems to behave
quite well, no mouse-jerkyness and so far I havn't heard any skips, but
it can take some time until a skip occurs.

With X reniced to -10 it feels like the wiggle_a_window while a
'make -j10' and a movie is playing gets a bit more sluggish.

And sawfish still takes 30 second naps when executing a bunch of
aumix's.

-- 
/Martin

Never argue with an idiot. They drag you down to their level, then beat you with experience.

  reply	other threads:[~2003-03-07 20:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5.2.0.9.2.20030307093435.01a8fe88@pop.gmx.net>
2003-03-07  9:30 ` [patch] "HT scheduler", sched-2.5.63-B3 Ingo Molnar
     [not found] ` <Pine.LNX.4.44.0303071003060.6318-100000@localhost.localdom ain>
2003-03-07  9:38   ` Mike Galbraith
2003-03-07 10:03     ` [patch] "interactivity changes", sched-2.5.64-B2 Ingo Molnar
2003-03-07 14:45       ` Ingo Molnar
     [not found]       ` <Pine.LNX.4.44.0303071543480.12493-100000@localhost.localdo main>
2003-03-07 15:44         ` Mike Galbraith
2003-03-07 18:50           ` Ingo Molnar
2003-03-07 18:55             ` Linus Torvalds
2003-03-07 19:10             ` Linus Torvalds
2003-03-07 19:13               ` Ingo Molnar
2003-03-07 19:31               ` Ingo Molnar
     [not found]     ` <Pine.LNX.4.44.0303071049500.7326-100000@localhost.localdom ain>
2003-03-07 10:23       ` Mike Galbraith
2003-03-07 12:54         ` Mike Galbraith
2003-03-07 13:27           ` Mike Galbraith
2003-03-07 14:43             ` Ingo Molnar
2003-03-07 20:34               ` Martin Josefsson
2003-03-07 20:39                 ` Ingo Molnar
2003-03-07 21:05                   ` Martin Josefsson [this message]
2003-03-07 21:47                     ` Martin Josefsson
2003-03-07 21:03                 ` David Lang
2003-03-07 21:13                   ` Martin Josefsson
2003-03-07 23:05                     ` Helge Hafting

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=1047071156.29990.5.camel@tux.rsn.bth.se \
    --to=gandalf@wlug.westbo.se \
    --cc=akpm@digeo.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rml@tech9.net \
    --cc=torvalds@transmeta.com \
    /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®