From: Avi Kivity <avi@redhat.com>
To: Rik van Riel <riel@redhat.com>
Cc: J Louis <handstogether8@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux scheduler capabilities for batch jobs.
Date: Mon, 01 Jun 2009 20:04:29 +0300 [thread overview]
Message-ID: <4A240A1D.8020906@redhat.com> (raw)
In-Reply-To: <4A240479.9040907@redhat.com>
Rik van Riel wrote:
> J Louis wrote:
>
>> If it was possible to tell
>> the scheduler that it was OK not to be fair when scheduling these
>> processes, I think the total runtime could be reduced if it put some
>> of the processes to sleep while others completed. Is there a way to
>> tell the scheduler it is allowed to do this? Should there be?
>
> There is no way to do this currently, but I suspect that it
> would not be too difficult to add.
>
> Of course, if you have two tasks that are each a little larger
> than memory, your idea could lead to one of the processes being
> starved forever. This is probably not acceptable :)
>
> In fact, one single batch process that is swapping could trigger
> the algorithm you described, halting itself. Your idea would
> need very carefuly implementation to avoid these kinds of issues,
> but I believe it could definately be done.
Some king of interaction between the swap token and the scheduler,
perhaps, for SCHED_BATCH processes.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-01 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 13:41 Linux scheduler capabilities for batch jobs J Louis
2009-06-01 16:40 ` Rik van Riel
2009-06-01 17:04 ` Avi Kivity [this message]
2009-06-03 21:14 ` Bill Davidsen
2009-06-02 4:57 ` Mike Galbraith
2009-06-17 9:38 ` Pavel Machek
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=4A240A1D.8020906@redhat.com \
--to=avi@redhat.com \
--cc=handstogether8@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.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 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.