From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Assistance with a dual-core machine.
Date: Sun, 24 Jun 2007 18:32:51 +0800 [thread overview]
Message-ID: <000301c7b64b$053dd810$2518a8c0@bouncy> (raw)
In-Reply-To: <000a01c7b647$edc2d350$6401a8c0@YOUR3ADE1B78A3>
This is not possible. You can not tell certain threads to run on certain
cores without modifying the code itself. Also the problems with
speechdup/speech dispatcher on multi-core systems relate to the fact that
multiple threads run concurrently rather than running in a pre-emptive
manner.
That is to say on a single core only one process runs at a time; with each
process scheduled into running one after the other.
The code in speechdup/speech dispatcher needs to be rewritten to take into
account the possibility of multiple threads running at once, and your only
solution to running this stabily on your system is to disable your second
core or run and test cvs code.
Without testers it will take far longer to debug these problems; and unless
you are willing to run a single core you sacrifice stability regardless of
whether the code is cvs or not.
cvs is not difficult to use; and you simply check out a source tree which
you then build.
If you are not used to building from source; perhaps it is necessary to wait
for the next stable release of these tools that will be stable and aware of
smp systems.
Regards, Kerry.
----- Original Message -----
From: "Keith Hinton" <keithint38@CommSpeed.net>
To: <speakup@braille.uwo.ca>
Sent: Sunday, June 24, 2007 6:10 PM
Subject: Assistance with a dual-core machine.
> Hello all on the ilst,
> At this time, (although) I am sure that CVS SpeechD-up/Dispatcher sounds
> great, I do not wish to test it..and
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Keith Hinton
` Samuel Thibault
` Kerry Hoath [this message]
` Jan Buchal
` Tomas Cerha
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='000301c7b64b$053dd810$2518a8c0@bouncy' \
--to=kerry@gotss.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).