From: Clarence Dang <dang@kde.org>
To: linux-msdos@vger.kernel.org
Subject: Re: unofficial prerelease 1.1.3.2 for testing
Date: Wed, 19 Jun 2002 20:41:54 +1000 [thread overview]
Message-ID: <200206192041.54246.dang@kde.org> (raw)
In-Reply-To: <3D0CB6BF.1000409@yahoo.com>
On Mon, 17 Jun 2002 02:03, Stas Sergeev wrote:
> Hello.
>
> Bart Oldeman wrote:
> > Please test the improved joystick support from Clarence Dang: it looks
> > very nice, but I don't have a joystick. He claims it works faster if
> > you enable pthreads (see compiletime-settings), but I experienced DPMI
> > crashes that way (DJGPP gcc immediately nukes DOSEMU), so left that out
> > by default. Can anyone confirm?
>
> Well, as I don't have a joystick, I
> can only confirm that dosemu doesn't
> even start on my machine when I enable
> pthreads. No problems with them disabled
> though.
>
Hi everyone,
I just ran the joystick code (with pthreads) on a little-used machine and it
froze...the logs report that it got a load average of 63 within 1 second of
starting DOSEMU. Later examination showed that it was randomly spawning new
threads uncontrollably! On another machine, it works fine...
So, just to be safe, you should probably turn off pthreads (as Bart Oldeman
and Stas Sergeev have pointed out). I'm curious though as to why pthreads
can cause so much trouble?
The performance increase with pthreads on with joystick support is not
significant at all on my machine (Pentium II) but is largely theoretical.
Thanks!
Clarence
next prev parent reply other threads:[~2002-06-19 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-16 16:03 unofficial prerelease 1.1.3.2 for testing Stas Sergeev
2002-06-19 10:41 ` Clarence Dang [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-16 13:57 Bart Oldeman
2002-06-16 13:55 ` Bart Oldeman
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=200206192041.54246.dang@kde.org \
--to=dang@kde.org \
--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