From: Jakub Jelinek <jakub@redhat.com>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Dan Kegel <dank@kegel.com>, linux-kernel@vger.kernel.org
Subject: Re: Hardware limits on numbers of threads?
Date: Wed, 18 Sep 2002 03:05:23 -0400 [thread overview]
Message-ID: <20020918030523.D12870@devserv.devel.redhat.com> (raw)
In-Reply-To: <200209180643.g8I6hBp29508@Port.imtp.ilyichevsk.odessa.ua>; from vda@port.imtp.ilyichevsk.odessa.ua on Wed, Sep 18, 2002 at 09:37:58AM -0200
On Wed, Sep 18, 2002 at 09:37:58AM -0200, Denis Vlasenko wrote:
> On 18 September 2002 04:43, 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?
>
> It is true that on x86 you have only 8192 different segment selectors
> at a time. Nobody says you can't modify segment descriptors on demand.
>
> If I'm not mistaken, Linux kernel does precisely this. It has per-CPU
> allocated GDT entries, not per-task.
That page has been written way before set_thread_area(2) (and other kernel
threading changes) were written.
Jakub
next prev parent reply other threads:[~2002-09-18 7:00 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
2002-09-18 7:29 ` Giuliano Pochini
2002-09-18 11:37 ` Denis Vlasenko
2002-09-18 7:05 ` Jakub Jelinek [this message]
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=20020918030523.D12870@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=dank@kegel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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