9 More Discussions You Might Find Interesting
1. Programming
hi,
I have two basic questions, I will be really grateful if I receive any
comment from you,
I have an MPI code where I am trying to implement OpenMP directives.
The machine where I run the code has 16 cores. I run the code with
export OMP_NUM_THREADS=2
mpirun -np 4 ./exec
If I... (0 Replies)
Discussion started by: armando_2011
0 Replies
2. Programming
I am using a large code-base that compiled successfully before using make with a makefile and cmake. However, now that I'm trying to use openmp with it, I'm now getting the errors
undefined reference to `omp_get_thread_num'
undefined reference to `omp_get_num_threads'I don't think this... (0 Replies)
Discussion started by: larry burns
0 Replies
3. Programming
Dear Linux users,
I'm a noob at openmp, gcc and c programming. I can run my own openmp code in terminal with no problem, eg. gcc -fopenmp program.c -o program.
But now I'm trying to compile and run another person's code, it contains a makefile and multiple .c and .h files. I don't know how to... (2 Replies)
Discussion started by: pigeon151
2 Replies
4. HP-UX
Hi folks,
I am trying to run more than 8 threads in OpenMP team on my HP-UX 11i v3 system (without root access), but NO success.
Compiler: aCC A.06.26
I tried to setup: OMP_NUM_THREADS, omp_set_num_threads(), max_thread_proc=1000, nkthread=8416, set_dynamic=0
Machine has 2 processors... (1 Reply)
Discussion started by: ATveretinov
1 Replies
5. UNIX for Advanced & Expert Users
I wonder if someone knows what is the rationale behind linking function calls of the POSIX threads library at link-time vs. run-time.
For example, if I create the following program:
#include <pthread.h>
void noop() {
return;
}
int main() {
pthread_self();
pthread_atfork(noop,... (1 Reply)
Discussion started by: jsimsa
1 Replies
6. Programming
Hi,
I am new to posix threads. The no of threads to be created depends on the runtime. If I get the number of threads,
I need to forward declare
pthread_t mythread;
how to do that can I use pointers and use malloc()??
I also have another question. The pthread_join is used to make... (0 Replies)
Discussion started by: brett01
0 Replies
7. UNIX for Advanced & Expert Users
Hi,
consider the code below:
#include <stdio.h>
.
.
struct myStruct
{
char *message ;
int id;
};
.
.
.
void *thread_function( void *ptr );
nt main()
{
pthread_t thread1, thread2 ,thread3 ;
struct myStruct nico1; (2 Replies)
Discussion started by: Behnaz
2 Replies
8. Programming
I created multiple POSIX threads (on readhat Linux) in a C program in my app. What I am doing is - I am creating threads equal to the number of CPUs in the system and and equal number of instances of a certain data structure, basically a queue implementation. I am assigning one ID to the thread... (2 Replies)
Discussion started by: radiatejava
2 Replies
9. Programming
Hello !
Let's supose I have a main function in C , and two POSIX threads. I give you an example down :
int main() {
int something;
char else;
void *FirstThread();
void *SecondThread();
..
<start those two pthreads ..>
return 0;}
void *FirstThread() { ... }
void *SecondThread()... (2 Replies)
Discussion started by: !_30
2 Replies
NPTL(7) Linux Programmer's Manual NPTL(7)
NAME
nptl - Native POSIX Threads Library
DESCRIPTION
NPTL (Native POSIX Threads Library) is the GNU C library POSIX threads implementation that is used on modern Linux systems.
NPTL and signals
NPTL makes internal use of the first two real-time signals (signal numbers 32 and 33). One of these signals is used to support thread can-
cellation and POSIX timers (see timer_create(2)); the other is used as part of a mechanism that ensures all threads in a process always
have the same UIDs and GIDs, as required by POSIX. These signals cannot be used in applications.
To prevent accidental use of these signals in applications, which might interfere with the operation of the NPTL implementation, various
glibc library functions and system call wrapper functions attempt to hide these signals from applications, as follows:
* SIGRTMIN is defined with the value 34 (rather than 32).
* The sigwaitinfo(2), sigtimedwait(2), and sigwait(3) interfaces silently ignore requests to wait for these two signals if they are speci-
fied in the signal set argument of these calls.
* The sigprocmask(2) and pthread_sigmask(3) interfaces silently ignore attempts to block these two signals.
* The sigaction(2), pthread_kill(3), and pthread_sigqueue(3) interfaces fail with the error EINVAL (indicating an invalid signal number)
if these signals are specified.
* sigfillset(3) does not include these two signals when it creates a full signal set.
NPTL and process credential changes
At the Linux kernel level, credentials (user and group IDs) are a per-thread attribute. However, POSIX requires that all of the POSIX
threads in a process have the same credentials. To accommodate this requirement, the NPTL implementation wraps all of the system calls
that change process credentials with functions that, in addition to invoking the underlying system call, arrange for all other threads in
the process to also change their credentials.
The implementation of each of these system calls involves the use of a real-time signal that is sent (using tgkill(2)) to each of the other
threads that must change its credentials. Before sending these signals, the thread that is changing credentials saves the new creden-
tial(s) and records the system call being employed in a global buffer. A signal handler in the receiving thread(s) fetches this informa-
tion and then uses the same system call to change its credentials.
Wrapper functions employing this technique are provided for setgid(2), setuid(2), setegid(2), seteuid(2), setregid(2), setreuid(2), setres-
gid(2), setresuid(2), and setgroups(2).
CONFORMING TO
For details of the conformance of NPTL to the POSIX standard, see pthreads(7).
NOTES
POSIX says that any thread in any process with access to the memory containing a process-shared (PTHREAD_PROCESS_SHARED) mutex can operate
on that mutex. However, on 64-bit x86 systems, the mutex definition for x86-64 is incompatible with the mutex definition for i386, meaning
that 32-bit and 64-bit binaries can't share mutexes on x86-64 systems.
SEE ALSO
credentials(7), pthreads(7), signal(7), standards(7)
Linux 2015-08-08 NPTL(7)