linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>,
	Daniel Gryniewicz <dang@fprintf.net>
Cc: Helge Hafting <helgehaf@aitel.hist.no>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Memory? Re: O(1) scheduler & interactivity improvements
Date: Mon, 23 Jun 2003 21:21:01 +0200	[thread overview]
Message-ID: <200306232121.02432.roger.larsson@skelleftea.mail.telia.com> (raw)
In-Reply-To: <1056394770.587.8.camel@teapot.felipe-alfaro.com>

On måndagen den 23 juni 2003 20.59, Felipe Alfaro Solana wrote:
> On Mon, 2003-06-23 at 18:21, Daniel Gryniewicz wrote:
> > > So then, why I can easily starve the X11 server (which should be marked
> > > interactive), Evolution or OpenOffice simply by running "while true; do
> > > a=2; done". Why don't they get an increased priority boost to stop the
> > > from behaving so jerky?
> >
> > You're own metric will kill you here.  You're while true; loop is
> > running in the shell, which is interactive (it has accepted user in put
> > in the past) and can therefore easily starve anything else.  You need a
> > an easy way to make an interactive process non-interactive, and that's
> > what these threads are all about, making interactive threads
> > non-interactive (and the other way around) in a fashion that maximises
> > the user experience.  A history of user input is not necessarily a good
> > metric, as many non-interactive CPU hogs start out life as interactive
> > threads (like your loop above).
>
> OK, replace "while true; ..." with a parallel kernel compile, for
> example, and the effect, on a 700Mhz laptop, is nearly the same: you can
> easily starve XMMS, and X11 feels jerky. Changing between virtual
> desktops in KDE produces the same effect, also.

And you are shure that you do not fill up your RAM?
(700MHz laptop does not sound like lots of RAM...)

* Parallel kernel compile, unlimited?
* Changing virtual desktops might be memory limited too...

Check with 'vmstat'

/RogerL

-- 
Roger Larsson
Skellefteå
Sweden

  reply	other threads:[~2003-06-23 19:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-22 16:07 O(1) scheduler & interactivity improvements Felipe Alfaro Solana
2003-06-22 20:00 ` Davide Libenzi
2003-06-23 12:50   ` Jesse Pollard
2003-06-23  8:09 ` Helge Hafting
2003-06-23 10:18   ` Felipe Alfaro Solana
2003-06-23 16:21     ` Daniel Gryniewicz
2003-06-23 18:59       ` Felipe Alfaro Solana
2003-06-23 19:21         ` Roger Larsson [this message]
2003-06-23 16:47     ` Helge Hafting
2003-06-24 18:12       ` Bill Davidsen
2003-06-25 21:41         ` Helge Hafting
     [not found]       ` <5.2.0.9.2.20030624215008.00ce73b8@pop.gmx.net>
2003-06-26  9:59         ` Helge Hafting
2003-06-26 10:39           ` Mike Galbraith
2003-06-26 14:50           ` Bill Davidsen
2003-06-26 23:10           ` Timothy Miller
     [not found]           ` <Pine.LNX.3.96.1030626104733.17562D-100000@gatekeeper.tmr.c om>
2003-06-27  6:36             ` Mike Galbraith
2003-06-27  8:18               ` Helge Hafting
2003-06-27  9:46                 ` Mike Galbraith
2003-06-27 11:39                   ` Helge Hafting
2003-06-27 12:18                     ` Mike Galbraith
2003-06-28  3:51                   ` Bill Davidsen
     [not found]                   ` <Pine.LNX.3.96.1030627234408.25848A-100000@gatekeeper.tmr.c om>
2003-06-28  5:44                     ` Mike Galbraith
2003-06-28 14:34                       ` Helge Hafting
2003-06-29  6:08                         ` Mike Galbraith
2003-06-30 13:37                       ` Bill Davidsen
2003-06-27  6:54           ` jw schultz

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=200306232121.02432.roger.larsson@skelleftea.mail.telia.com \
    --to=roger.larsson@skelleftea.mail.telia.com \
    --cc=dang@fprintf.net \
    --cc=felipe_alfaro@linuxmail.org \
    --cc=helgehaf@aitel.hist.no \
    --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).