linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "James A. Sutherland" <jas88@cam.ac.uk>
Cc: happz <happz@dragon.cz>, linux-mm@kvack.org
Subject: Re: suspend processes at load
Date: 19 Apr 2001 22:11:28 -0600	[thread overview]
Message-ID: <m1g0f4rz0v.fsf@frodo.biederman.org> (raw)
In-Reply-To: "James A. Sutherland"'s message of "Thu, 19 Apr 2001 21:14:48 +0100"

"James A. Sutherland" <jas88@cam.ac.uk> writes:

> On Mon, 19 Mar 2001 21:06:55 +0100, you wrote:
> 
> >What about this: give to process way how to tell kernel "it is not
> >good to suspend me, because there are process' that depend on me and
> >wouldn't be blocked." Syscall or /proc filesystem could be used.
> >
> >It is not the way how to say which process should be suspended but a
> >way how to say which could NOT - usefull for example for X server, may
> >be some daemons, aso.
> 
> Possibly; TBH, I don't think it's worth it. Remember, "suspending" X
> would just stop your mouse moving etc. for (e.g.) 5 seconds; in fact,
> that should block most graphical processes, which may well resolve the
> thrashing in itself!

Actually we should only apply suspension and the like to SCHED_OTHER.
The realtime scheduling classes should be left as is.  If an
application is safe to run realtime, it should be o.k. in the
thrashing situation. 

Also actually suspending a realtime process would be a violation of
the realtime scheduling guarantees, where with SCHED_OTHER you can be
expected to be suspended at any time.

Eric
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2001-04-20  4:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-19 20:06 happz
2001-04-19 20:14 ` James A. Sutherland
2001-04-20  4:11   ` Eric W. Biederman [this message]
2001-04-20  6:35     ` James A. Sutherland

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=m1g0f4rz0v.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=happz@dragon.cz \
    --cc=jas88@cam.ac.uk \
    --cc=linux-mm@kvack.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