The description of the OS says that separate memory regions are not necessary because integers cannot be converted into pointers, and if you don't have a pointer, you cannot access memory. This sounds nice enough to start with, but it is actually quite insufficient.
In the Intel world, we had read only code segments. But there were alias selectors used by the OS to load code into read only code segments. I suspect there will be a way eventually to get a rogue pointer when a user program pretends to be a system routine, then it is over. All it takes is one vulnerability and the entire system architecture is compromised.
Also the lack of C is troubling. Java and C# are not enough for me. Maybe this is a good OS for after I am dead.
Secure the machine with a password, but don't watch what you are typing when you enter it. Now no one knows the password, and even though they have you, what you know, your body... They cannot get into the system. Of course you can't either, but you didn't say anything about that being a requirement. What you have, what you know, and who you are... The big three..... We are all waiting for a fourth security principle to make things better:-)
I saw stuff like that at Digital Research when I worked there. Character mode displays of file drawers that popped open and displays folder tab labels and such. Around GEM time or so.
I have the 2.4GHz MacBook Pro 17" glossy HD. What a beautiful machine. 4GB-ram and 150G-hd. I use it hours a day. Mail, web browsing, iTunes, DVD playing. It does everything I want. The 17" 1920x1024 display gives me all the real estate I want and I have not been bothered by the glossy screen even once. There may be people that use them in environments with higher light levels than I do that have problems. I use mine in a home environment and couldn't be happier. If there are actual color calibration issues, I wouldn't know because I am not a pro photo guy laying out important real color stuff. I just wanted the best Apple notebook available for development, and I feel I did the right thing. I am not sure why I went "glossy", but it has been fine.
If studies might be 1,000 times off, this study might be 1,000 times off and the hadron collider odds might be a million times off instead of 1,000 times off. Just my take on this:-)
IANABCS (... Scientist) but it seems to me that when particles hit the atmosphere, they have had to deal with the Van Allen belt first and may be at less energetic levels by then.
Having spoken with a noted cosmologist about "Expansion", I have a great deal of respect for the forces involved around the time of the big bang, when in a very small amount of time, a great deal of mass arrived in a big darn hurry. I am not as worried about the creation of a small black hole that lasts a few milliseconds as an event where a huge amount of mass arrives unexpectedly in a very short period of time. This would also be bad, unless of course it happened to be something cool like millions of tons of some precious metal that would benefit personkind. Even then, it would be inconvenient for billions of tons of material to arrive unexpectedly in a small space. A billion tons of diamonds arriving would bum out the diamond merchants. A billion tons of arsenic would create a new supersite. A billion tons of gold would be good for the Swiss national treasury. A billion tons of Viagra would be a WTO problem considering patents and trademarks...
On hard disks, there are two kinds of bad sectors. Those that were that way from the start because of manufacturing defects, and some dynamically occurring ones. In the industry, there are general guidelines about how many bad sectors per platter are considered reasonable. With SSD, all sectors start out useable and eventually (dynamically) fail. A used hard drive may have more dynamically failed sectors than it started out with, but that number would probably never increase past a few percent. The SSDs though eventually reach the point where the dynamically failed sectors are 100%. So I would buy a used hard drive expecting it might have a little more vibration, perhaps several dozen dynamically failed sectors, and the MTBF would be shorter. SSDs though are a different game. You are betting that the drive will last until you are ok simply replacing it, before it dies completely. Things will get very dicey towards the end, and you are hoping not to be there by then. SSDs are kind of like cars that last so long, then they start dying and you can't keep them running no matter how many repairs you make. Like cars, leasing SSDs and getting a new one each year would be the way to go, and buying used ones would be risky. If it sounds like I am down on them, maybe I am. If I had an application where I needed solid state storage and was willing to pay more and replace them often, they could be just the solution. When they become cheap enough, using them and discarding them when they get cranky would be fine.
As SSD drives come into the market used, how will people know how close these drives are to "used up". That is to say, we will have to worry that these cheap drives on ebay will have lots of "bad" spots that can no longer be written. We are going to be needing a program or device of some kind that can certify the state of a drive so as to set a fair value on it. I expect a lot of unhappy people when used drives get installed and start failing soon after. There will have to be some pretty sleazy warrantees to cover used SSDs.
Are you telling me that XP running in a VM on a powerbook is about the same as Mac OS X running native?
That makes no sense to me. If you say that is what you are seeing, I must believe you, but your information doesn't match up with my information.
I can see a world where an XP lookalike would be good enough, except that the same things that keep Linux off the desktop would work against ReactOS. Anything less than 99.99% compatibility would cause a support crisis and could not be sold to businesses. Businesses are sold Microsoft solutions because they work within certain criteria and can be supported, sort of.
As an engineer I can see that ReactOS would solve many problems exc ept the funny stuff like Active X and programs that need contemporary APIs and SQL Server. Unfortunately, most users seem to need the whole tamale of Microsoft features to run their mission critical collection of programs, unless they make a concerted effort on a corporate level to use something else like Macs, and sometimes Linux. There may well come a day when ReactOS hits a compatibility point equal to where Microsoft was five years ago, and for many people that might be good enough, but no for a critical mass of the population I am afraid. I put my money on Apple and Mac OS X, for the long term. Unless Microsoft just stays around and we have to suffer with them until we die.
I have an iMac 17" flat panel 886MHz PPC 1GB-ram machine that is currently running Mac OS X 10.5.6. Everything is working very well except that there are problems getting a flash version for PowerPC that will work with youtube. Otherwise the machine is running better than WIndows would be on an older machine of approximately the same caliber.
I recently loaded Windows XP on a 3GHz 2GB-ram toshiba P35-S609 and the gui response is very sluggish. Much worse in fact than the GUI on the iMac. The machine was so sluggish in fact that I had my mouth hanging open that people put up with this. I have been using the Mac for about three years now, and gave up Windows about two years ago. I am not a fanboi, but rather a systems programmer with a lot of experience in operating systems. I understand things like what goes into smooth mouse tracking. I have to give Apple the prize for systems that run faster each release, and systems that run well on limited resource hardware.
After a few years, DOS users knew enough to use the "dir" command to look for the install.bat or setup.bat and run that. I realize that there were some that had to read the installation instructions to get that far, but it worked for most of us. At any time Microsoft could have recognized that the autorun was causing more trouble than it was worth and turned it off in the next update. Also they could have worked something out with the InstallShield people as that tool was used by almost everybody. But it is a sin that Microsoft didn't even take the first step, and have not yet here in 2009.
Probably the reason they didn't was certain devices had to get drivers loaded or they would not work at all, like a stick that needs a codec installed to access its encrypted content. to boot.
The US government had so much trouble with USB sticks that the made a policy that government employees were not allowed to insert them. If the US govt had half a clue, they would have made Microsoft change the defaults to save their own butts. I just cannot understand this.;-(
I had a Bendix G15 in high school. It wasn't very reliable though and a tube would burn out every couple of hours. Of course if you wanted it to go faster, you could rotate the variac and the drum memory would speed up. I cannot say I have seen any reviews on that in a few years though, good or bad.
I started to do some contracting work for a telecom startup in Rohnert Park. I showed up to find out what I needed to do and what tools I would have to buy to perform my job. They balked when I sounded like I expected them to purchase a license for my development system seat, and wanted to give me some CDRs instead. I declined and invested the first month's wages in my own licensed copy of the compiler involved.
The next time I went in, they offered me a pirated copy of the latest update to QEMM. I said no thanks, went home, and my wife ordered me a copy of the software from Ingram Micro. Several days later I started to hear the bad news. The development manager had gone around the company and updated every desktop machine in the place with a single unprotected floppy. The next day, each machine as it was turned on started erasing all files on the hard disk, deltree c:\*.*/S style. This development manager couldn't quite believe what he was seeing so he went around and turned on each and every machine in the place and watched while they creamed themselves, one after the next.
The moral of this story is obvious. I was working for the guy and he insisted that I take the QEMM floppy home with me. I admit I did, but I threw it away when I got home. He called me in a panic Saturday morning with a sad story and asked if I had used the software. I can not say whether he was happy for me or not when I said I had not and had just ordered a clean copy.
So this is not about covering your ass with an email or a letter. It is about doing the right things for the right reasons and being able to see quickly thereafter the benefits of honesty. I cannot say who this company was because I signed an NDA, but you would recognize the name if I told you. I am not perfect. I have made mistakes. I have sinned in my life. But by this time I had learned some and was straight arrow about software licensing. I still am and have not to this day downloaded any MP3 music that violates copyrights. People don't understand my position about this, and I can only try to lead by example. But this story about the QEMM floppy that spread the virus and destroyed every desktop in the corporation is one hundred percent true, I swear it. On a Bible.
I have never met Tim personally. I did try to speak with him once about a book idea, and I was told to put my idea in email and maybe he would look at it. He got his big start way back when in the X Window days with the publishing of the X Window books. They were a big seller, version after version.
I think O'Reilly was a fairly large employer in Sebastopol though and I am sure that this layoff is hitting the city hard. I used to live down the way from them in Rohnert Park and Petaluma. To the best of my knowledge the employees were rather attached to their jobs there and the job market in general in Sonoma County has sucked since foreign telecom manufacturers (Singapore mainly) ruined the telecom alley.
I am not sure where these people will get technical jobs next as highly trained technical people have been flipping burgers in Sonoma County for a few years now. I had to leave the area after twenty years over lack of jobs. Good luck to them.
As I said, I don't know Tim personally, but I would like to think he felt paternal about his Sebastopol employees and probably hated having to lay off anyone.
As I said though, he was arrogant to me, so I am not sure about what I just said. I think Sonoma people are nice in general and I hoped he was, but who knows?
I was a consultant at a well known company in Marin County. I was hired in for a few months and given something difficult to do. Getting a handle on the job was the first hurdle, and had I received some cooperation, the team's group goals would have been completed in a more timely fashion. When I asked a few simple questions to get started, I was rebuffed with, "What? You don't know how to ^%*&^%?". The guy I asked was the only one who knew a certain trick, and depended on that to keep his job. After my fist contracting period ended, they asked me to stay, but the team dynamics stunk, and continued to stink until the company hired a women CEO and things changed mightily. I didn't ask this fellow to do my job, I just asked which way was up, and had he bothered to give me twenty minutes of help, I could have been a real asset to the department. It is obviously important to get your own work done, but helping out a little builds team trust and cohesion. Good managers know this.
There used to be a market for TCP stacks, and popular applications tended to be bundled with them. I realize that the day did come when TCP was a natural to support in the OS, but including the protocols doesn't imply all applications should be part of the OS as well. Just because X Window gets shipped with LINUX doesn't mean XEYES is part of the OS. Know what I mean?
Microsoft has used their position in the OS market to affect the quality and timing of third party software written to run on their operating systems. Application and language tools written by Microsoft benefitted from access to proprietary information about the OS that was not available to other developers. An example of this was back when MFC used to be bundled with third party compilers. These compilers, such as Borland, and Watcom... usually had down level versions of MFC. Developers were coerced into buying and using MS tools to get immediate access to supported APIs. The third party compilers were often better code generators, but could not compete because of unfair licensing practices.
I didn't have a spare PC for this so I loaded up an instance of Virtual PC on a fairly fast Windows XP box. The install went ok, and after it rebooted, a dialog box came up suggesting that I load the Virtualizing enhancements. I did that, then after the reboot the system could not come up and complained of driver problems. Then it asked if it should repair itself. I said yes, and after a while it asked if restoring a previous context would be ok. Afterwards the system was fonctional again but there was no sound support, so either the create soundblaster support in Virtual PC didn't work, or the Windows 7 use of the SB driver. Otherwise it was interesting to see the new system
One interesting note though was that as soon as it was up, it complained that it could not detect an anti-virus program loaded. This was kind of a surprise because I was sort of hoping this new version of Windows would be more resistant to viruses and would not immediately need a third party AV program on day one.
I understand what you are saying. It is just that in the old days, we took the input, and processed it and did some output. Now we have to take the input, then initiate a number of threads that must be managed and synchronized and disposed of properly. This sounds all just slightly more complex than usual, except that the mechanics of managing multiple threads, memory allocation and garbage collection and inter-thread communication multiplies the complexity of the development quite a lot, not to mention the difficulty in debugging.
A program with multiple threads never executes exactly the same way twice as the threads do not execute synchronously. Real-time conditions and resources affect when and how these threads start, what resources they have, and which run faster. Synchronization and communication of and between the threads adds to the complexity.
This is as opposed to a single threaded program that runs more or less exactly the same from one execution to the next starting at the beginning and running until the end. What can change is the amount of resources and the CPU load during execution, but you can single step a single threaded program multiple times and see the same path each time. With multi-threaded, it is like a pinball machine with multiple balls at the same time. They go different ways and sometimes they bounce off each other.
The hardware manufacturers dumped this multi-core technology on us without laying a foundation of software engineering support. I would like to see some standards and language support beyond the normal thread packages inherited from Unix. Intel's threaded toolbox is one candidate. Maybe NIST should have a contest, like they do with encryption methods. I just don't think it is efficient for us to have to roll our own multi-core support at the application level, if that means rolling our own debugging support at the same time. The more cores, the harder this is.
It looks to me like today, Windows uses 1.x cores and what is left over gets used by whatever applications are trying to run. Since Microsoft always uses up the majority of the resources, memory and cycles after each advance in technology, maybe we should have them use one core for system threads, and devote at least one other for the applicationm threads. I know this is not exactly simple because of the way code slips back and for between kernel and user space as operating systems evolve, but you know what I mean.
I am looking at developing an application that utilizes multiple cores (on Apple Mac Pro) and I have questions like how do you keep the OS hands off the cores you want to delegate to the application. I have about six threads I want assigned to their own cores exclusively. Core ownership is not handled in a straight forward manner. We have a ways to go before these things become clear.
Slashdot Mirror
In the Intel world, we had read only code segments. But there were alias selectors used by the OS to load code into read only code segments. I suspect there will be a way eventually to get a rogue pointer when a user program pretends to be a system routine, then it is over. All it takes is one vulnerability and the entire system architecture is compromised.
Also the lack of C is troubling. Java and C# are not enough for me. Maybe this is a good OS for after I am dead.
Secure the machine with a password, but don't watch what you are typing when you enter it. Now no one knows the password, and even though they have you, what you know, your body... They cannot get into the system. Of course you can't either, but you didn't say anything about that being a requirement. What you have, what you know, and who you are... The big three..... We are all waiting for a fourth security principle to make things better :-)
I saw stuff like that at Digital Research when I worked there. Character mode displays of file drawers that popped open and displays folder tab labels and such. Around GEM time or so.
Functions built with ternary math could efficiently returns statuses such as (abort, retry, ignore). :-)
I have the 2.4GHz MacBook Pro 17" glossy HD. What a beautiful machine. 4GB-ram and 150G-hd. I use it hours a day. Mail, web browsing, iTunes, DVD playing. It does everything I want. The 17" 1920x1024 display gives me all the real estate I want and I have not been bothered by the glossy screen even once. There may be people that use them in environments with higher light levels than I do that have problems. I use mine in a home environment and couldn't be happier. If there are actual color calibration issues, I wouldn't know because I am not a pro photo guy laying out important real color stuff. I just wanted the best Apple notebook available for development, and I feel I did the right thing. I am not sure why I went "glossy", but it has been fine.
If studies might be 1,000 times off, this study might be 1,000 times off and the hadron collider odds might be a million times off instead of 1,000 times off. Just my take on this :-)
Having spoken with a noted cosmologist about "Expansion", I have a great deal of respect for the forces involved around the time of the big bang, when in a very small amount of time, a great deal of mass arrived in a big darn hurry. I am not as worried about the creation of a small black hole that lasts a few milliseconds as an event where a huge amount of mass arrives unexpectedly in a very short period of time. This would also be bad, unless of course it happened to be something cool like millions of tons of some precious metal that would benefit personkind. Even then, it would be inconvenient for billions of tons of material to arrive unexpectedly in a small space. A billion tons of diamonds arriving would bum out the diamond merchants. A billion tons of arsenic would create a new supersite. A billion tons of gold would be good for the Swiss national treasury. A billion tons of Viagra would be a WTO problem considering patents and trademarks...
On hard disks, there are two kinds of bad sectors. Those that were that way from the start because of manufacturing defects, and some dynamically occurring ones. In the industry, there are general guidelines about how many bad sectors per platter are considered reasonable. With SSD, all sectors start out useable and eventually (dynamically) fail. A used hard drive may have more dynamically failed sectors than it started out with, but that number would probably never increase past a few percent. The SSDs though eventually reach the point where the dynamically failed sectors are 100%. So I would buy a used hard drive expecting it might have a little more vibration, perhaps several dozen dynamically failed sectors, and the MTBF would be shorter. SSDs though are a different game. You are betting that the drive will last until you are ok simply replacing it, before it dies completely. Things will get very dicey towards the end, and you are hoping not to be there by then. SSDs are kind of like cars that last so long, then they start dying and you can't keep them running no matter how many repairs you make. Like cars, leasing SSDs and getting a new one each year would be the way to go, and buying used ones would be risky. If it sounds like I am down on them, maybe I am. If I had an application where I needed solid state storage and was willing to pay more and replace them often, they could be just the solution. When they become cheap enough, using them and discarding them when they get cranky would be fine.
As SSD drives come into the market used, how will people know how close these drives are to "used up". That is to say, we will have to worry that these cheap drives on ebay will have lots of "bad" spots that can no longer be written. We are going to be needing a program or device of some kind that can certify the state of a drive so as to set a fair value on it. I expect a lot of unhappy people when used drives get installed and start failing soon after. There will have to be some pretty sleazy warrantees to cover used SSDs.
Are you telling me that XP running in a VM on a powerbook is about the same as Mac OS X running native? That makes no sense to me. If you say that is what you are seeing, I must believe you, but your information doesn't match up with my information.
As an engineer I can see that ReactOS would solve many problems exc ept the funny stuff like Active X and programs that need contemporary APIs and SQL Server. Unfortunately, most users seem to need the whole tamale of Microsoft features to run their mission critical collection of programs, unless they make a concerted effort on a corporate level to use something else like Macs, and sometimes Linux. There may well come a day when ReactOS hits a compatibility point equal to where Microsoft was five years ago, and for many people that might be good enough, but no for a critical mass of the population I am afraid. I put my money on Apple and Mac OS X, for the long term. Unless Microsoft just stays around and we have to suffer with them until we die.
I recently loaded Windows XP on a 3GHz 2GB-ram toshiba P35-S609 and the gui response is very sluggish. Much worse in fact than the GUI on the iMac. The machine was so sluggish in fact that I had my mouth hanging open that people put up with this. I have been using the Mac for about three years now, and gave up Windows about two years ago. I am not a fanboi, but rather a systems programmer with a lot of experience in operating systems. I understand things like what goes into smooth mouse tracking. I have to give Apple the prize for systems that run faster each release, and systems that run well on limited resource hardware.
Probably the reason they didn't was certain devices had to get drivers loaded or they would not work at all, like a stick that needs a codec installed to access its encrypted content. to boot.
The US government had so much trouble with USB sticks that the made a policy that government employees were not allowed to insert them. If the US govt had half a clue, they would have made Microsoft change the defaults to save their own butts. I just cannot understand this. ;-(
I had a Bendix G15 in high school. It wasn't very reliable though and a tube would burn out every couple of hours. Of course if you wanted it to go faster, you could rotate the variac and the drum memory would speed up. I cannot say I have seen any reviews on that in a few years though, good or bad.
The next time I went in, they offered me a pirated copy of the latest update to QEMM. I said no thanks, went home, and my wife ordered me a copy of the software from Ingram Micro. Several days later I started to hear the bad news. The development manager had gone around the company and updated every desktop machine in the place with a single unprotected floppy. The next day, each machine as it was turned on started erasing all files on the hard disk, deltree c:\*.* /S style. This development manager couldn't quite believe what he was seeing so he went around and turned on each and every machine in the place and watched while they creamed themselves, one after the next.
The moral of this story is obvious. I was working for the guy and he insisted that I take the QEMM floppy home with me. I admit I did, but I threw it away when I got home. He called me in a panic Saturday morning with a sad story and asked if I had used the software. I can not say whether he was happy for me or not when I said I had not and had just ordered a clean copy.
So this is not about covering your ass with an email or a letter. It is about doing the right things for the right reasons and being able to see quickly thereafter the benefits of honesty. I cannot say who this company was because I signed an NDA, but you would recognize the name if I told you. I am not perfect. I have made mistakes. I have sinned in my life. But by this time I had learned some and was straight arrow about software licensing. I still am and have not to this day downloaded any MP3 music that violates copyrights. People don't understand my position about this, and I can only try to lead by example. But this story about the QEMM floppy that spread the virus and destroyed every desktop in the corporation is one hundred percent true, I swear it. On a Bible.
That was pleasantly frank Bruce, thanks for that.
I think O'Reilly was a fairly large employer in Sebastopol though and I am sure that this layoff is hitting the city hard. I used to live down the way from them in Rohnert Park and Petaluma. To the best of my knowledge the employees were rather attached to their jobs there and the job market in general in Sonoma County has sucked since foreign telecom manufacturers (Singapore mainly) ruined the telecom alley.
I am not sure where these people will get technical jobs next as highly trained technical people have been flipping burgers in Sonoma County for a few years now. I had to leave the area after twenty years over lack of jobs. Good luck to them.
As I said, I don't know Tim personally, but I would like to think he felt paternal about his Sebastopol employees and probably hated having to lay off anyone.
As I said though, he was arrogant to me, so I am not sure about what I just said. I think Sonoma people are nice in general and I hoped he was, but who knows?
I was a consultant at a well known company in Marin County. I was hired in for a few months and given something difficult to do. Getting a handle on the job was the first hurdle, and had I received some cooperation, the team's group goals would have been completed in a more timely fashion. When I asked a few simple questions to get started, I was rebuffed with, "What? You don't know how to ^%*&^%?". The guy I asked was the only one who knew a certain trick, and depended on that to keep his job. After my fist contracting period ended, they asked me to stay, but the team dynamics stunk, and continued to stink until the company hired a women CEO and things changed mightily. I didn't ask this fellow to do my job, I just asked which way was up, and had he bothered to give me twenty minutes of help, I could have been a real asset to the department. It is obviously important to get your own work done, but helping out a little builds team trust and cohesion. Good managers know this.
Your posting was one of the more poignant ones I have read here today. Well said.
There used to be a market for TCP stacks, and popular applications tended to be bundled with them. I realize that the day did come when TCP was a natural to support in the OS, but including the protocols doesn't imply all applications should be part of the OS as well. Just because X Window gets shipped with LINUX doesn't mean XEYES is part of the OS. Know what I mean?
Microsoft has used their position in the OS market to affect the quality and timing of third party software written to run on their operating systems. Application and language tools written by Microsoft benefitted from access to proprietary information about the OS that was not available to other developers. An example of this was back when MFC used to be bundled with third party compilers. These compilers, such as Borland, and Watcom... usually had down level versions of MFC. Developers were coerced into buying and using MS tools to get immediate access to supported APIs. The third party compilers were often better code generators, but could not compete because of unfair licensing practices.
Maybe he should go to work for some other company where they hire executives with experience in throwing chairs...
Tell them what you're going to tell them... Tell them what your telling them... and tell them what you told them. Right?
One interesting note though was that as soon as it was up, it complained that it could not detect an anti-virus program loaded. This was kind of a surprise because I was sort of hoping this new version of Windows would be more resistant to viruses and would not immediately need a third party AV program on day one.
A program with multiple threads never executes exactly the same way twice as the threads do not execute synchronously. Real-time conditions and resources affect when and how these threads start, what resources they have, and which run faster. Synchronization and communication of and between the threads adds to the complexity.
This is as opposed to a single threaded program that runs more or less exactly the same from one execution to the next starting at the beginning and running until the end. What can change is the amount of resources and the CPU load during execution, but you can single step a single threaded program multiple times and see the same path each time. With multi-threaded, it is like a pinball machine with multiple balls at the same time. They go different ways and sometimes they bounce off each other.
The hardware manufacturers dumped this multi-core technology on us without laying a foundation of software engineering support. I would like to see some standards and language support beyond the normal thread packages inherited from Unix. Intel's threaded toolbox is one candidate. Maybe NIST should have a contest, like they do with encryption methods. I just don't think it is efficient for us to have to roll our own multi-core support at the application level, if that means rolling our own debugging support at the same time. The more cores, the harder this is. It looks to me like today, Windows uses 1.x cores and what is left over gets used by whatever applications are trying to run. Since Microsoft always uses up the majority of the resources, memory and cycles after each advance in technology, maybe we should have them use one core for system threads, and devote at least one other for the applicationm threads. I know this is not exactly simple because of the way code slips back and for between kernel and user space as operating systems evolve, but you know what I mean. I am looking at developing an application that utilizes multiple cores (on Apple Mac Pro) and I have questions like how do you keep the OS hands off the cores you want to delegate to the application. I have about six threads I want assigned to their own cores exclusively. Core ownership is not handled in a straight forward manner. We have a ways to go before these things become clear.