Commenter Waleri Todorov recalled that the global descriptor table (GDT), which is one of the places that selectors are defined, is limited to 1024 selectors. Does that mean that there is a hard limit of 1024 threads?<\/p>\n
The question was in the context of how Windows NT for the 80386 managed the thread environment block (TEB), namely, by using the No, it doesn’t, because nobody said that the distinct values had to be different simultaneously.<\/p>\n Let’s start with a single-processor system. That single processor is executing only one thread at a time, so there needs to be only one valid value for You can see this in the debugger. Break into a multithreaded program and look at the value of the This trick works even on multiprocessor systems. Each processor has its own GDTR internal register, so instead of sharing a single GDT for all processors, you can give each processor its own GDT.<\/p>\n So I guess this puts the theoretical maximum number of processors supported by an x86-based system at around twenty-four million, because that would exhaust all of kernel mode address space just for GDTs.\u00b2<\/p>\n No, wait, that’s still not the limit, because each processor also gets its own page table. After all, that’s how two processors can be executing threads from different processes (and therefore in different address spaces). So the theoretical limit is basically until you run out of memory<\/i>.<\/p>\n But I suspect you’ll run into other problems long before you add that twenty-four-millionth processor.<\/p>\n \u00b9 Bit 2 is clear for GDT selectors and set for LDT selectors, so you can infer that \u00b2 I calculated this by dividing 2\u00b3\u00b9 by They don’t all have to be different simultaneously.<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[2],"class_list":["post-102503","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-history"],"acf":[],"blog_post_summary":" They don’t all have to be different simultaneously.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/102503","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=102503"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/102503\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=102503"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=102503"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=102503"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}fs<\/code> register to point to the per-thread data. The point is that there are at most 1024 possible distinct values for the fs<\/code> register to have, so does this implicitly limit the number of threads to 1024?<\/p>\nfs<\/code> at a time. When the processor changes threads, the definition of that selector is updated to refer to the TEB for the incoming thread. Using selectors to access another thread’s TEB is not part of the ABI; all that is required is that you can use fs<\/code> to access your own<\/i> TEB.<\/p>\nfs<\/code> register. On my system it’s 0x0053<\/code>. Switch to another thread and look at the value of the fs<\/code> register. It’s the same value: 0x0053<\/code>. Every thread has the same selector in fs<\/code>. What happens is that each time the processor changes threads, the GDT entry for 0x0053<\/code> is updated to refer to the TEB of the thread that is being scheduled.\u00b9<\/p>\n0x0053<\/code> is a GDT selector.<\/p>\n0x60<\/code>, which is my presumed minimum size for a GDT. A selector whose numeric value is 0x0053<\/code> implies that the GDT is at least 0x0058<\/code> bytes in size, because that’s how big you need to be to get to a selector value of 0x0053<\/code> in the first place.<\/p>\n","protected":false},"excerpt":{"rendered":"