
Hyperthreading with Creamware
yeah everybody... it shows a big disrespect for huubOn 2003-06-13 21:18, hubird wrote:
snif snif, my name is Hubird, not Hubrid, why are so many of us calling me hubrid, I'm not hybrid at all, I love just my little big mac, woeahhh

andy
the lunatics are in the hall
the lunatics are in the hall
- paulrmartin
- Posts: 2445
- Joined: Sun May 20, 2001 4:00 pm
- Location: Montreal, Canada
It's fairly complicated, but these might help...
http://www.anandtech.com/cpu/showdoc.html?i=1746
http://www6.tomshardware.com/cpu/20021227/index.html
http://www6.tomshardware.com/cpu/20021202/index.html
Cheers,
Will
http://www.anandtech.com/cpu/showdoc.html?i=1746
http://www6.tomshardware.com/cpu/20021227/index.html
http://www6.tomshardware.com/cpu/20021202/index.html
Cheers,
Will
- paulrmartin
- Posts: 2445
- Joined: Sun May 20, 2001 4:00 pm
- Location: Montreal, Canada
From the second link:
"...Threading an existing serial application increases the complexity of the application, Intel says. Sharing of resources, such as global data, can introduce common parallel programming errors such as storage conflicts and other race conditions. Debugging such problems is difficult as they are non-deterministic, and introducing debugging probes, such as print statements, can mask these errors."
Sharing of resources, such as gobal data...: This caught my eye.
Do you think this would be a cause for concern for us?
<font size=-1>[ This Message was edited by: paulrmartin on 2003-06-14 17:04 ]</font>
"...Threading an existing serial application increases the complexity of the application, Intel says. Sharing of resources, such as global data, can introduce common parallel programming errors such as storage conflicts and other race conditions. Debugging such problems is difficult as they are non-deterministic, and introducing debugging probes, such as print statements, can mask these errors."
Sharing of resources, such as gobal data...: This caught my eye.
Do you think this would be a cause for concern for us?
<font size=-1>[ This Message was edited by: paulrmartin on 2003-06-14 17:04 ]</font>
- paulrmartin
- Posts: 2445
- Joined: Sun May 20, 2001 4:00 pm
- Location: Montreal, Canada
This is a VERY encouraging thread:
http://www.intel.com/home/do_more/music ... rpheus.htm
Very encouraging indeed!
http://www.intel.com/home/do_more/music ... rpheus.htm
Very encouraging indeed!

it looks like "never ending story". so...
i just did recording from cubase to wavelab (asio 24bit source -> stm1632 -> 24bit wave dest.) and i had a lot of clicks and distortions.
then i update computer from "acpi multyprocessors fucken pc" to...


... and now the recorded tracks are clear - problem is solved.
fynaly, "acpi pc" mode works without problems to me instead of all other modes.
i will like if someone with "acpi multyprocessors pc" can try to do the same: try to do recordings from cubase to wavelab (asio 24bit source -> stm1632 -> 24bit wave dest.)????
i just did recording from cubase to wavelab (asio 24bit source -> stm1632 -> 24bit wave dest.) and i had a lot of clicks and distortions.
then i update computer from "acpi multyprocessors fucken pc" to...


... and now the recorded tracks are clear - problem is solved.
fynaly, "acpi pc" mode works without problems to me instead of all other modes.
i will like if someone with "acpi multyprocessors pc" can try to do the same: try to do recordings from cubase to wavelab (asio 24bit source -> stm1632 -> 24bit wave dest.)????
- paulrmartin
- Posts: 2445
- Joined: Sun May 20, 2001 4:00 pm
- Location: Montreal, Canada
you mean that i do recording in the stereo cubase's chanell?!
yes! if i use asio only, than works perfect in every case. so i can connect asio to asio and do record in cubase.
something is wrong with wdm drivers if computer is in "acpi multyprocessors pc" mode - something with recordings by useing "wave dest". playback is correct.
i will like if someone can try the same?
btw: i found that pulsar works better in modes with 16 irq's instead of 22.
_________________
<font size=-2>got my mojo working, but it just won't work on you</font>
<font size=-1>[ This Message was edited by: sandrob on 2003-06-16 12:59 ]</font>
<font size=-1>[ This Message was edited by: sandrob on 2003-06-16 13:05 ]</font>
yes! if i use asio only, than works perfect in every case. so i can connect asio to asio and do record in cubase.
something is wrong with wdm drivers if computer is in "acpi multyprocessors pc" mode - something with recordings by useing "wave dest". playback is correct.
i will like if someone can try the same?
btw: i found that pulsar works better in modes with 16 irq's instead of 22.
_________________
<font size=-2>got my mojo working, but it just won't work on you</font>
<font size=-1>[ This Message was edited by: sandrob on 2003-06-16 12:59 ]</font>
<font size=-1>[ This Message was edited by: sandrob on 2003-06-16 13:05 ]</font>
Hi Sandrob,
great! Your config makes very much sense. The 2nd CPU is not a real CPU, so I can imagine that WDM drivers could get confused when they want to do parallel processing and then, because in reality it is only one CPU that can do the trick only with a little latency -however small the amount may be-, they find out that it is not really parallel. A normal WDM is not prepared to do latency correction in this case, so the result may be nasty.
The trick with HT is that the CPU is divided in very small time slices with TWO input units instead of one, one for the even numbered slices, one for the odd. So the capacity of the CPU can be used more efficiently in normal use. In continous use (arithmetic!, MPEG4 etc.) there is no advantage.
But usually we have more programs running, not only SFP.
So your solution seems to become our standard here, I suppose.
Thanks for your excellent investigation!
great! Your config makes very much sense. The 2nd CPU is not a real CPU, so I can imagine that WDM drivers could get confused when they want to do parallel processing and then, because in reality it is only one CPU that can do the trick only with a little latency -however small the amount may be-, they find out that it is not really parallel. A normal WDM is not prepared to do latency correction in this case, so the result may be nasty.
The trick with HT is that the CPU is divided in very small time slices with TWO input units instead of one, one for the even numbered slices, one for the odd. So the capacity of the CPU can be used more efficiently in normal use. In continous use (arithmetic!, MPEG4 etc.) there is no advantage.
But usually we have more programs running, not only SFP.
So your solution seems to become our standard here, I suppose.
Thanks for your excellent investigation!

i like to share my new experiences but i have no enough knowledge to know what's realy happends here.
so, in the "acpi mode" (note: this is not "acpi uniprocessor mode") i still have 2 virtual cpu's in managger and i don't have any problem with wdm drivers!!
so, i guess that pulsar can handle with 16 irq's instead of 22?!
so, in the "acpi mode" (note: this is not "acpi uniprocessor mode") i still have 2 virtual cpu's in managger and i don't have any problem with wdm drivers!!
so, i guess that pulsar can handle with 16 irq's instead of 22?!