From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-msdos@vger.kernel.org
Subject: Re: dosemu with different speed
Date: Sat, 24 Apr 2004 19:00:22 -0500 [thread overview]
Message-ID: <20040425000022.GC24996@dbz.icequake.net> (raw)
In-Reply-To: <20040423195728.GE31941@dbz.icequake.net>
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
On Sat, Apr 24, 2004 at 09:32:39PM +0100, Andrew Brooks wrote:
> Ryan Underwood wrote:
> > What do you mean by "speed"? You want different scheduling
> > priorities
> > for each one? Can just use 'nice'.
>
> I have a DOS application which must respond to an interrupt within a
> certain amount of time. I have tried using nice to raise the priority
> but it still misses occasionally.
Yep. DOSEMU is not DOS. If you have realtime constraints, we must look
into calling sched_setscheduler() on user's behalf to set policy to
SCHED_RR or SCHED_FIFO. But that will require root permission. It
is also possible for your machine to be completely locked-up if the DOS
task fails in any way.
> Do you think it's safe to run dosemu in the realtime scheduling class?
> (in which case I would leave hogthreshold at 1 = nicest)
I think DOSEMU itself is mostly safe. The problem is the DOS program
you are running. If it ever goes into an uncontrollable loop (i.e.
polling with interrupts disabled), you are screwed and will have to
reboot when running SCHED_FIFO. SCHED_RR should not be so bad because
the scheduler is guaranteed to seize control periodically, but only
other SCHED_RR processes are guaranteed to get any CPU time. So you
would have to have a SCHED_RR bash running too in order to be able to
gain control of the other process.
--
Ryan Underwood, <nemesis@icequake.net>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-25 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 8:14 dosemu with different speed kandan bala
2004-04-23 19:57 ` Ryan Underwood
2004-04-25 0:00 ` Ryan Underwood [this message]
2004-04-28 6:44 ` kandan bala
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=20040425000022.GC24996@dbz.icequake.net \
--to=nemesis-lists@icequake.net \
--cc=linux-msdos@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