public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: linux-kernel@vger.kernel.org
Subject: Hardware limits on numbers of threads?
Date: Tue, 17 Sep 2002 23:43:26 -0700	[thread overview]
Message-ID: <3D88208E.8545AAA2@kegel.com> (raw)

http://people.redhat.com/drepper/glibcthreads.html says:

> Hardware restrictions put hard limits on the number of 
> threads the kernel can support for each process. 
> Specifically this applies to IA-32 (and AMD x86_64) where the thread
> register is a segment register. The processor architecture 
> puts an upper limit on the number of segment register values 
> which can be used (8192 in this case).

Is this true?  Where does the limit come from?
- Dan

             reply	other threads:[~2002-09-18  6:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18  6:43 Dan Kegel [this message]
2002-09-18  7:02 ` Hardware limits on numbers of threads? Ulrich Drepper
2002-09-18 16:30   ` Dan Kegel
2002-09-18 19:19   ` Jamie Lokier
2002-09-19  9:36   ` Andi Kleen
2002-09-18  7:29 ` Giuliano Pochini
2002-09-18 11:37 ` Denis Vlasenko
2002-09-18  7:05   ` Jakub Jelinek
2002-09-18 11:57 ` Brian Gerst

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=3D88208E.8545AAA2@kegel.com \
    --to=dank@kegel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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