From: Ulrich Drepper <drepper@redhat.com>
To: Dan Kegel <dank@kegel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hardware limits on numbers of threads?
Date: Wed, 18 Sep 2002 00:02:24 -0700 [thread overview]
Message-ID: <3D882500.2000105@redhat.com> (raw)
In-Reply-To: 3D88208E.8545AAA2@kegel.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dan Kegel wrote:
> 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?
This was and is true with the kernel before 2.5.3<mumble> when Ingo
introduced TLS support since the thread specific data had to be
addressed via LDT entries and the LDT holds at most 8192 entries. The
GDT based solution now implemented in the kernel has no such limitation
and the number of threads you can create with the new thread library is
only limited by system resources.
- --
- ---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE9iCUE2ijCOnn/RHQRAgqyAJ0e88AQXpxXoHrvZCxIhfZXJFJP9QCbBlCL
nXUfQkt00sX+XsHg89OZz+k=
=NkZd
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-09-18 6:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 6:43 Hardware limits on numbers of threads? Dan Kegel
2002-09-18 7:02 ` Ulrich Drepper [this message]
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=3D882500.2000105@redhat.com \
--to=drepper@redhat.com \
--cc=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