Amount of threads per task?
Hi L4 Hackers! When creating new threads within the L4Linux kernel, I "sometimes" (whatever that means) get the following output and error: *l4lx | l4lx_thread_create: Created thread 0e.1a (Command) --Thread names exhausted!--------------------------------IP: 0050758e What does that mean? After pressing "g", the system continues running. However when I try to kill the thread later, I get the following: --Unknown TID to delete thread name!---------------------IP: 0050760a Is it not possible to create more than 0x19 = 25 threads within the L4Linux kernel? Or am I doing anything wrong? Regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft@sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 519 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
When creating new threads within the L4Linux kernel, I "sometimes" (whatever that means) get the following output and error:
*l4lx | l4lx_thread_create: Created thread 0e.1a (Command) --Thread names exhausted!--------------------------------IP: 0050758e
What does that mean? After pressing "g", the system continues running. However when I try to kill the thread later, I get the following:
--Unknown TID to delete thread name!---------------------IP: 0050760a
Is it not possible to create more than 0x19 = 25 threads within the L4Linux kernel? Or am I doing anything wrong?
You don't make a mistake. The thread library has a default setting for the maximum number of threads. You can increase this number by setting something like const int l4thread_max_threads = 100; in your application. Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE7qaCP5ijxgQLUNkRAj3nAJ0TmY4S8inH/sDUFrfOc06s/O1NkACfbcuV E5Dx/UyxbRaYT1vXxBV/YI4= =K/sq -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Forget my last answer. I overlooked that you had an L4Linux problem. The solution is nearly the same, but in L4Linux you need to change the definition of L4LX_THREAD_NO_THREADS in asm/l4lxapi/generic/thread_gen.h Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE7qcvP5ijxgQLUNkRAnNOAKCaP/DlUcLt+8vRAiX5zIgbIcVG5ACfUdPd 6cUlfbmo0VZ3NWBB/3NlL88= =u5Ho -----END PGP SIGNATURE-----
Hi Björn!
Forget my last answer. I overlooked that you had an L4Linux problem. The solution is nearly the same, but in L4Linux you need to change the definition of L4LX_THREAD_NO_THREADS in asm/l4lxapi/generic/thread_gen.h Ok, I see. Is there a reason why it is set explicitly to 24? Are there any side effects of increasing that number?
Regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft@sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 519 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
L4LX_THREAD_NO_THREADS in asm/l4lxapi/generic/thread_gen.h Ok, I see. Is there a reason why it is set explicitly to 24? Are there any side effects of increasing that number?
I assume 24 is as good as any other number. L4Linux consumes some more memory with more threads enabled. Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE7uSeP5ijxgQLUNkRAkVsAJoDz6zxgpVbbSDb7KFfClazcVV/1QCeLJF9 xaQ7xm1o3ylOq/ctQnBxWGU= =F3u0 -----END PGP SIGNATURE-----
On Fri Aug 25, 2006 at 12:21:45 +0200, Oskar Senft wrote:
Forget my last answer. I overlooked that you had an L4Linux problem. The solution is nearly the same, but in L4Linux you need to change the definition of L4LX_THREAD_NO_THREADS in asm/l4lxapi/generic/thread_gen.h Ok, I see. Is there a reason why it is set explicitly to 24?
Because that's usually enough for common usage.
Are there any side effects of increasing that number?
Increased memory usage. Adam -- Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
participants (3)
-
Adam Lackorzynski -
Bjoern Doebel -
Oskar Senft