Thread implementation in Linux


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Thread implementation in Linux
# 1  
Old 04-13-2013
Thread implementation in Linux

I read about Thread implementation in linux. it says a thread is treated as a process. that means every thread (which should be light weight) has it's own task_struct (which is quite heavy, tipically 1.5kb). still results favors linux then other operating system which have additional support for Threads. Does any one have explanation how Linux is favorable?Smilie
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Linux

Thread specific data from linux core dump

How do i get pointer to thread's local storage or thread specific data while analyzing core dump for linux ? i use pthread_setspecific to store some data in the pthread's local stoare. my multi threaded program on linux crashed, and i want to see what is stored in current running thread's... (2 Replies)
Discussion started by: vishwasungal
2 Replies

2. Linux

Linux Thread Stack Size pthread_attr_setstacksize

I have MultiThreaded Application in Linux. I am Setting the stack size using pthread_attr_setstacksize. The stack size i set is greter than PTHREAD_STACK_MIN i.e. 16384 bytes for my system. i am setting the stack size to 17408 bytes, and my application crashes due to insufficient stack size.... (1 Reply)
Discussion started by: Kedar Sabnis
1 Replies

3. UNIX for Dummies Questions & Answers

Linux Device Driver: how can an ISR wake up a user-thread?

Hi all, Is it possible to do the following in Linux (kernel 2.6.x): - A user-space thread goes to "sleep". Using any call/mechanism - On a hardware generated interrupt, the Interrupt handler (ISR) "wakes" the sleeping user-thread. I have seen wait_event() and wake_up() but it appears... (1 Reply)
Discussion started by: agaurav
1 Replies

4. Infrastructure Monitoring

Need implementation of TCP, SNMP and WIMAX in Linux

Hi, Can anyone please provide the Open Source implmentation of the Following Protocols in Linux Operating Systems. A. SNMP B. TCP C. WIMAX MAC layer protocol. Thaniks Saurav (2 Replies)
Discussion started by: sauravbh
2 Replies

5. Programming

Thread pooling in cpp on gnu linux

I m newb to thread pooling. I have to create a cpp application using thread pooling for gnu/linux machine. I didn't get too much on the net. Can any one give me the references to source code or conceptual document of thread pooling in cpp for gnu/linux. Any help will be appreciated. (4 Replies)
Discussion started by: ps_sach
4 Replies

6. Linux

usel level TCP implementation for linux

Does anyone know of a user level implementation of the TCP stack for Linux? Thanks, - sumati (1 Reply)
Discussion started by: sumati01
1 Replies

7. Programming

Frame buffer implementation in Linux

At present, Iam working on Linux Framebuffer device console. I have a doubt sir. Please solve this. *How to display a string or a character in Frame buffer in C language? *What is the library file (is it <linux/fb.h> or other one?) used to do all I/O function manipulations like printing,... (0 Replies)
Discussion started by: chandra80
0 Replies

8. Linux

Linux Hyper-thread support?

Hello all, I'm looking in to building a Redhat/Windows machine for myself and was wondering if Redhat linux support 800Mhz front side bus speed or hyper-thread? If so would I have to recompile the kernel to enable this feature? Thanks (3 Replies)
Discussion started by: larry
3 Replies
Login or Register to Ask a Question
THREAD-KEYRING(7)					     Linux Programmer's Manual						 THREAD-KEYRING(7)

NAME
thread-keyring - per-thread keyring DESCRIPTION
The thread keyring is a keyring used to anchor keys on behalf of a process. It is created only when a thread requests it. The thread keyring has the name (description) _tid. A special serial number value, KEY_SPEC_THREAD_KEYRING, is defined that can be used in lieu of the actual serial number of the calling thread's thread keyring. From the keyctl(1) utility, '@t' can be used instead of a numeric key ID in much the same way, but as keyctl(1) is a program run after forking, this is of no utility. Thread keyrings are not inherited across clone(2) and fork(2) and are cleared by execve(2). A thread keyring is destroyed when the thread that refers to it terminates. Initially, a thread does not have a thread keyring. If a thread doesn't have a thread keyring when it is accessed, then it will be created if it is to be modified; otherwise the operation fails with the error ENOKEY. SEE ALSO
keyctl(1), keyctl(3), keyrings(7), persistent-keyring(7), process-keyring(7), session-keyring(7), user-keyring(7), user-session-keyring(7) Linux 2017-03-13 THREAD-KEYRING(7)