From: Andi Kleen <ak@muc.de>
To: Ulrich Drepper <drepper@redhat.com>
Cc: linux-kernel@vger.kernel.org, dank@kegel.com
Subject: Re: Hardware limits on numbers of threads?
Date: 19 Sep 2002 11:36:11 +0200 [thread overview]
Message-ID: <m3n0qe8gok.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <3D882500.2000105@redhat.com>
Ulrich Drepper <drepper@redhat.com> writes:
> 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.
It also was alwas incorrect for x86-64/64bit progreams, which do not
use a LDT entry for each thread.
-Andi
next prev parent reply other threads:[~2002-09-19 20:20 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
2002-09-18 16:30 ` Dan Kegel
2002-09-18 19:19 ` Jamie Lokier
2002-09-19 9:36 ` Andi Kleen [this message]
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=m3n0qe8gok.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=dank@kegel.com \
--cc=drepper@redhat.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