All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org>
To: jeremy@goop.org, akpm@digeo.com
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, efault@gmx.de
Subject: Re: [patch] sched-2.5.64-D3, more interactivity changes
Date: Wed, 19 Mar 2003 12:30:33 +0100	[thread overview]
Message-ID: <20030319113033.19451.qmail@linuxmail.org> (raw)

----- Original Message ----- 
From: Jeremy Fitzhardinge <jeremy@goop.org> 
Date: 	18 Mar 2003 23:13:01 -0800 
To: Andrew Morton <akpm@digeo.com> 
Subject: Re: [patch] sched-2.5.64-D3, more interactivity changes 
 
> I'm still getting starvation problems.  If I run xmms with the "Goom" 
> visualizer (with the window large enough that it is CPU-bound), then 
> type a command into a shell window (say, ps), it will not run the 
> command until I close or shrink the goom window.  xmms itself plays 
> fine, though sometimes it fails to go to the next track, apparently for 
> the same reason (ie, it starts the next track when I disable the 
> visualizer). 
 
Well, I'm also experiencing starvation problems with CPU-bound 
loads. For example, I'm converting all my music collection from 
MP3 to OGG, and when using "oggenc" to convert from WAV to 
OGG, the system becomes pretty unresponsive: running commands 
on a terminal (for example a "ps axf") takes forever, unless you 
stop (Ctrl+S) the "oggenc" process. 
 
To avoid this, I had to lower "oggenc" priority using renice. Using 
renice <PID> +20 helped with starvation :-) 
 
Thanks! 
 
   Felipe 
  
-- 
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr

Powered by Outblaze

             reply	other threads:[~2003-03-19 11:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19 11:30 Felipe Alfaro Solana [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-19 11:40 [patch] sched-2.5.64-D3, more interactivity changes Felipe Alfaro Solana
2003-03-18  0:28 Sean Estabrooks
2003-03-17 10:21 Ingo Molnar
2003-03-17 18:01 ` Martin J. Bligh
2003-03-19  5:52 ` Andrew Morton
2003-03-19  6:31   ` Joshua Kwan
2003-03-19  7:13   ` Jeremy Fitzhardinge
2003-03-19  8:21     ` Mike Galbraith
2003-03-19 16:37       ` Jeremy Fitzhardinge
2003-03-19 16:51       ` Jim Houston

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=20030319113033.19451.qmail@linuxmail.org \
    --to=felipe_alfaro@linuxmail.org \
    --cc=akpm@digeo.com \
    --cc=efault@gmx.de \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.