From: Pavel Machek <pavel@ucw.cz>
To: J Louis <handstogether8@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux scheduler capabilities for batch jobs.
Date: Wed, 17 Jun 2009 11:38:51 +0200 [thread overview]
Message-ID: <20090617093851.GA1403@ucw.cz> (raw)
In-Reply-To: <6f41bd4b0906010641n1b360dffs6eaed72eb24f60f5@mail.gmail.com>
On Mon 2009-06-01 09:41:07, J Louis wrote:
> Hello All,
>
> I have been writing user land server code and increasingly I find
> myself writing resource management code which I think would be better
> handled by the scheduler. The problem can be described as "don't run
> this process if the machine is swapping." I would think that this
> would be a common enough need that it was already in the kernel. I'm
> hoping it is and I have simply overlooked it (part of the reason for
> this post,) but I've looked around a good bit and most of the
> scheduler enhancements have to do with real time and latency, not
> batch jobs.
>
> My problem is analogous to a parallel make. Say I have an 8 CPU
> machine, and I run "make -j8". If the total memory of the 8 jobs
> throws the machine into swap, it begins to thrash and runtime is
> awful. I believe this is aggravated by the scheduler trying to be
This seems to be racy by design.
make -j:
launch gcc1
gcc1 does preprocessing (10mb)
ok, still not swapping
launch gcc2
gcc2 does preprocessing (10mb)
...
gcc100 does preprocessing (10mb, 1GB total)
now gcc1..gcc100 start optimizing (100mb needed) and boom.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2009-06-17 9:44 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
2009-06-03 21:14 ` Bill Davidsen
2009-06-02 4:57 ` Mike Galbraith
2009-06-17 9:38 ` Pavel Machek [this message]
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=20090617093851.GA1403@ucw.cz \
--to=pavel@ucw.cz \
--cc=handstogether8@gmail.com \
--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