From: Jan Kandziora <jjj@gmx.de>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Limiting load of certain processes
Date: Wed, 27 Jun 2007 21:09:16 +0200 [thread overview]
Message-ID: <200706272109.17472.jjj@gmx.de> (raw)
In-Reply-To: <200706271606.48773.maximlevitsky@gmail.com>
Am Mittwoch, 27. Juni 2007 15:06 schrieb Maxim Levitsky:
>
> Well, I almost sure that this is not true,
> or maybe you are not using dosemu 1.4.0, and other one behaves differently.
>
> Anyway, if I run dosemu 1.4.0 with that setting and stock freedos
> command.com the cpu usage is well below 5%, and dosemu task is not reniced
> There are even times that I forget that dosemu is running.
>
It's like I wrote in the top post. The problem is not command.com or some
other freedos application, but an old, proprietary clipper DB application,
which, in a lot of situations, doesn't behave nice but loops while waiting
for user interaction.
I tested with dosemu 1.4.0 btw. With dosemu 1.2.x, clipper apps aren't even
working.
> Also I don't know why but dosemu 1.4.0 has new sound system that is way
> better that 1.2 one, but it is not enabled so you need to set $_sound=(2)
> to get it, what is nice is that this one uses SDL ( read alsa) for output,
> and has OPL3 emulation, so MIDI plays out of box
>
Nice, but out of my focus...
Kind regards
Jan
prev parent reply other threads:[~2007-06-27 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 17:50 Limiting load of certain processes Jan Kandziora
2007-06-21 18:26 ` Jan Engelhardt
2007-06-21 19:00 ` Jan Kandziora
2007-06-21 19:11 ` Jan Engelhardt
2007-06-26 1:44 ` Maxim Levitsky
2007-06-26 9:48 ` Jan Kandziora
2007-06-27 13:06 ` Maxim Levitsky
2007-06-27 19:09 ` Jan Kandziora [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=200706272109.17472.jjj@gmx.de \
--to=jjj@gmx.de \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox