From mint-bounce@lists.fishpool.fi  Wed Sep 10 11:17:30 2008
Subject: Re: [MiNT] Supexec taking one VBL?
From: Petr =?ISO-8859-1?Q?Stehl=EDk?= <pstehlik@sophics.cz>
To: Miro Kropacek <miro.kropacek@gmail.com>
Cc: Frank Naumann <fnaumann@boerde.de>, mint <mint@fishpool.com>
In-Reply-To: <c6533ef60809100522r3f039e08kb96617e8d15aa624@mail.gmail.com>
References: <48C415D6.605@gmail.com> <48C5617D.5060007@gmail.com>
	 <20080909104743.Q83829@antyk.obta.uw.edu.pl>
	 <c6533ef60809090250q439f7926t5cff7414e34da6cb@mail.gmail.com>
	 <20080909115952.R83829@antyk.obta.uw.edu.pl>
	 <c6533ef60809090337j392ff8acm5d22b4646681a290@mail.gmail.com>
	 <alpine.LFD.1.10.0809091305540.3969@localhost.localdomain>
	 <1221038419.13190.66.camel@petr>
	 <c6533ef60809100442x6c1d1e6eyaa0aceec1aaedcee@mail.gmail.com>
	 <1221047733.13190.85.camel@petr>
	 <c6533ef60809100522r3f039e08kb96617e8d15aa624@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-2
Date: Wed, 10 Sep 2008 15:42:47 +0200
Message-Id: <1221054167.6651.3.camel@joy>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1 
X-Approved-By: tjhukkan@fishpool.fi
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: pstehlik@sophics.cz
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id m8AFHTJA028478

Miro Kropacek píše v St 10. 09. 2008 v 14:22 +0200:
> This could be real problem, this frequent context switch, because we
> want to run the demo/game in multitasking, yes, but not for the prize
> of 30% performance decrease (due to too frequent switching). Maybe we
> could introduce some kind of application flag (in program header --
> "run as topmost/fullscreen/AES-less application" or something like
> that and it would mean the background processes will run in really low
> frequency and kernel will just switch between these user interrupt
> handlers (in any desired frequency).

Well that sounds like a real-time priority flag. Linux does have such
thing, AFAIK.

Petr