From: Ingo Molnar <mingo@elte.hu>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] optional non-interactive mode for cpu scheduler
Date: Tue, 2 Nov 2004 14:11:05 +0100 [thread overview]
Message-ID: <20041102131105.GA17535@elte.hu> (raw)
In-Reply-To: <4187854C.6000803@kolivas.org>
* Con Kolivas <kernel@kolivas.org> wrote:
> However the non-interactive mode addresses a number of different needs
> that seem to have come up. Specifically:
> I have had users report great success with such a mode on my own
> scheduler in multiple X session setups where very choppy behaviour
> occurs in mainline.
since SCHED_CPUBOUND would be inherited across fork(), it should be
rather easy to start an X session with all tasks as SCHED_CPUBOUND.
but i think the above rather points in the direction of some genuine
weakness in the interactivity code (i know, for which the fix is
staircase ;) which would be nice to debug.
> Many high performance computing people do not wish interactivity code
> modifying their choice of latency/distribution - admittedly this is a
> soft one.
well, SCHED_CPUBOUND would solve their needs too, right?
Ingo
next prev parent reply other threads:[~2004-11-02 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 5:31 [PATCH] optional non-interactive mode for cpu scheduler Con Kolivas
2004-11-02 12:52 ` Ingo Molnar
2004-11-02 13:02 ` Con Kolivas
2004-11-02 13:11 ` Ingo Molnar [this message]
2004-11-02 13:40 ` Con Kolivas
2004-11-02 13:52 ` Ingo Molnar
2004-11-02 17:17 ` Kyle Moffett
2004-11-03 9:16 ` Con Kolivas
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=20041102131105.GA17535@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--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