10-03-2009
Quote:
My question is this - Do POSIX multi-threads really allow for an optimal implementation of a micro-parallel algorithm? Or am I doing something wrong, because I am only using 45% of the power of my Quad-Core, when I should be maxing it out?
Who knows. You have not supplied us with any information that can enable us to help you. What operating system? What compiler and version? Which threading model? 1:1 or MxN or what? What compiler optimisations?
I will say this. POSIX threads would not be my choice for implementing a parallel algorithm.
9 More Discussions You Might Find Interesting
1. AIX
Hi,
what is concept of core in ibm platform?
I want to know how to find out no of core in cpu in aix i.e command
how to find out value of core?
Wheather any specification is there? (1 Reply)
Discussion started by: manoj.solaris
1 Replies
2. AIX
is there command which will display no of core per cpu in aix?
Regads,
Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
I want to know if in UNIX is it possible to distinguish between a CPU and a core through any command?
Thanks,
Vineet (1 Reply)
Discussion started by: vineetd
1 Replies
4. Linux Benchmarks
CPU/Speed: AMD Phenom(tm) 9950 Quad-Core Processor
Ram: 3.6 GB
Motherboard: Foxconn 7da-s
Bus:
Cache:
Controller:
Disk:
Load:
Kernel: Linux 2.6.26-2-amd64
Kernel ELF?:
pgms:
==============================================================
BYTE UNIX Benchmarks (Version... (0 Replies)
Discussion started by: migracho
0 Replies
5. AIX
Hi Friends-
What does it mean by 2 cpu cores, 3 cpu cores? Does it mean 2 separate cpus or what is it exactly ?
Kindly explain a bit in detail.
Thanks
panditt (4 Replies)
Discussion started by: deshaipet
4 Replies
6. Solaris
Hi,
I have 2 physical processor UltraSPARC-T2 with 32 virtual processors
I want to execute a perl program on 10 virtual processors.
I try prset command, but I don't see a difference.
psrset -c "created processor set 2" 1 2 3 4 5 6 7 8 9 10"
psrset -b 2 `pgrep program.pl`
Maybe... (8 Replies)
Discussion started by: falloutsam
8 Replies
7. HP-UX
hi every body
i want to know if i have server with hp-ux os if i did "machinfo" i will see no of cpu = for example 16
how can i know this is dual or quad core .
thanks (2 Replies)
Discussion started by: maxim42
2 Replies
8. Solaris
please help
does a cpu/memory module have a firmware ?? and do i need to check it before install the cpu/memory module in the motherboard ??
thnx (2 Replies)
Discussion started by: bahjatm
2 Replies
9. Red Hat
I would like to understand how many number of CPUs and cores do I have on my server based on following out put..
Few observations... Please correct me if I am wrong
Since Physical ID is same CPU is singe
It has 8 virtual processors
Hyper thrading is enabled since no of siblings are... (1 Reply)
Discussion started by: parth_buch
1 Replies
LEARN ABOUT SUSE
pthread_kill_other_threads_np
PTHREAD_KILL_OTHER_THREADS_NP(3) Linux Programmer's Manual PTHREAD_KILL_OTHER_THREADS_NP(3)
NAME
pthread_kill_other_threads_np - terminate all other threads in process
SYNOPSIS
#include <pthread.h>
void pthread_kill_other_threads_np(void);
DESCRIPTION
pthread_kill_other_threads_np() only has an effect in the LinuxThreads threading implementation. On that implementation, calling this
function causes the immediate termination of all threads in the application, except the calling thread. The cancellation state and cancel-
lation type of the to-be-terminated threads are ignored, and the cleanup handlers are not called in those threads.
CONFORMING TO
This function is a nonstandard GNU extension.
NOTES
pthread_kill_other_threads_np() is intended to be called just before a thread calls execve(2) or a similar function. This function is
designed to address a limitation in the obsolete LinuxThreads implementation whereby the other threads of an application are not automati-
cally terminated (as POSIX.1-2001 requires) during execve(2).
In the NPTL threading implementation, pthread_kill_other_threads_np() exists, but does nothing. (Nothing needs to be done, because the
implementation does the right thing during an execve(2).)
SEE ALSO
execve(2), pthread_setcancelstate(3), pthread_setcanceltype(3), pthread_cancel(3), pthreads(7)
COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2009-01-28 PTHREAD_KILL_OTHER_THREADS_NP(3)