From: "Keith Hinton" <keithint38@CommSpeed.net>
To: <speakup@braille.uwo.ca>
Subject: Regarding Dual-core processors
Date: Fri, 23 Feb 2007 16:21:39 -0700 [thread overview]
Message-ID: <000801c757a1$5eb48af0$6401a8c0@YOUR3ADE1B78A3> (raw)
Yes, Lorenzo Tailer,
I do have a dual-core processor.
We just tried an experiment with Arch Linux, kernel 2.6.10, 32-bit OS, and turned off the SMP option (therefore losing the second core on my AMD Athlon X2 dual-core processor.)
However, Hynec Hanky:
I want to report to you:
Speechd-up, and Speach-Dispatcher did not crash, (so the core loss was worth it.)
I believe now, that Lorenzo's testing was valuable. I want more background information on this spisific issue however..Can a developer of speech-Dispatcher or Speechd-up write more on this SMP v.s. Non-SMP kernel issue?
I don't see how having SMP off (therefore losing a core works) but it does. I am interested fore more details on this interesting issue. Why doesn't dual-core work? I can tell you that it does die, the entire thing, (Speech-Dispatcher, and Speechd-up) as long as SMP is enabled.
Regards,
--Keith
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000801c757a1$5eb48af0$6401a8c0@YOUR3ADE1B78A3' \
--to=keithint38@commspeed.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).