This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Fri, Jun 21, 2002 at 12:42:03PM +0200, Jakub Jelinek wrote: > On Fri, Jun 21, 2002 at 02:02:10PM +0400, Peter Zaitsev wrote: > > Also I would not agree about such architecture. Thread-per client > > architecture is quite convenient for many applications. Not only > > It may be convenient, but it also means you don't care > at all about wasting system resources (every thread currently eats some > unswappable kernel stack, its userland stack, etc.). Also, on IA-32 there > is hardware limitation that you can have only up to 8192 threads > in one application (though glibc limits this to 1024 threads normally). You are talking about Linux, right? But glibc also runs on other systems with other kernels which don't have the same limitation as Linux has. For example, L4 has very fast thread and almost everything can be swapped out. And you can perfectly have more than 8192 threads on IA-32, only Linux can't handle that. It's a software limitation, not a hardware limitation. In my implementation of pthreads I don't have any limit on stack sizes or number of threads. Jeroen Dekkers -- Jabber ID: jdekkers@jabber.org IRC ID: jeroen@openprojects GNU supporter - http://www.gnu.org
Attachment:
msg00104/pgp00000.pgp
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |