linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Pavel Machek <pavel@suse.cz>
Cc: Kevin Easton <s3159795@student.anu.edu.au>,
	linux-kernel@vger.kernel.org, riel@conectiva.com.br
Subject: Re: Scheduling of low-priority background processes
Date: Fri, 9 Nov 2001 10:39:59 -0700	[thread overview]
Message-ID: <200111091739.fA9Hdx107488@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <20011108123938.A45@toy.ucw.cz>
In-Reply-To: <20011106190757.A28090@beernut.flames.org.au> <20011106202212.A28518@beernut.flames.org.au> <20011108123938.A45@toy.ucw.cz>

Pavel Machek writes:
> Hi!
> > I foolishly muttered:
> > 
> > > What if the SCHED_IDLE behaviour only applies when the process 
> > > is in userspace? Couldn't scheduler compare the process's 
> > > instruction pointer against the kernel/user break point, and 
> > > if the process is in the kernel, then just treat it like a 
> > > normal process? 
> > 
> > ...eek.   I clearly wasn't thinking straight with that one.  There
> > isn't a (non-disgusting) way of determining in the scheduler if a
> > process is executing a syscall apart from sys_sched_yield, is there.
> 
> Actually, something similar was implemented. New process flag was
> added, and when process did syscall, it lost SCHED_IDLE flag, and it
> was returned to it when it went back to userland.

That's the sensible approach. Is anyone maintaining that patch and
sending it to Linus for inclusion?

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  parent reply	other threads:[~2001-11-09 17:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05 20:53 Scheduling of low-priority background processes Thomas Koeller
2001-11-05 21:08 ` Rik van Riel
2001-11-05 21:12   ` Thomas Koeller
2001-11-06  1:03 ` Rik van Riel
2001-11-06  8:07   ` Kevin Easton
2001-11-06  9:22     ` Kevin Easton
2001-11-08 12:39       ` Pavel Machek
2001-11-09 17:39       ` Richard Gooch [this message]
     [not found] <Pine.LNX.4.10.10111051722590.13543-100000@coffee.psychology.mcmaster.ca>
2001-11-05 23:30 ` Thomas Koeller

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=200111091739.fA9Hdx107488@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=riel@conectiva.com.br \
    --cc=s3159795@student.anu.edu.au \
    /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).