However, linking a particular managed thread to its ProcessThread was made deliberately difficult. Net provides the ability to access native operating system threads using the class, and this class has the ability to change the thread's processor affinity using the ProcessorAffinity property. ![]() I suppose it is still possible that other managed threads can share the same operating system thread, but this seems unlikely and is definitely not the case in any current. This guarantees that the managed thread will stay on the same operating system thread (so it does nothing on the default CLR host, as that is already true by default). It is possible to strengthen our confidence even for future versions of. Net 2.0's introduction, it is unlikely this will ever change. Given that this hasn't changed in all the years since. ![]() This never really went anywhere, so while there is no guarantee that a managed thread will always run on the same operating system thread, in practice this is always the case for all current. Net 2.0, and plans by the SQL Server team to implement. The separation between managed and operating system threads dates back to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |