Sponsored Content
Operating Systems HP-UX Spawn more than 8 threads OpenMP & HPUX Post 302741229 by DGPickett on Friday 7th of December 2012 04:03:14 PM
Old 12-07-2012
Not that into OpenMP, but still, not sure where you see one thread. I found this interesting: c++ - OpenMP threads executing on the same cpu core - Stack Overflow
 

7 More Discussions You Might Find Interesting

1. HP-UX

HPUX printers & plotters disable on a daily basis

HI all, I've been having issues with printers and plotters disabling with no reason at all...It could happen to the same workstation once a day or once a week..There is nothing consistant..I stop and restart the spooler, only then can I re-enable the disabled printer.... If anyone is... (0 Replies)
Discussion started by: Shutdown
0 Replies

2. UNIX for Advanced & Expert Users

UNIX 386 & HPUX

We have a C program which does the encryption and decryption. It is running fine in UNIX 386. But the same C program is giving different results in HP UX server. We found that the Ascii codes (output) are different. I don;t know why it is giving different results. How can we get the same output... (4 Replies)
Discussion started by: Rajeshsu
4 Replies

3. HP-UX

HPUX & Top Command

Hello, I'm a newbie to HPUX so please be patient :) I'm looking at top and it only shows 3 of the 8 cpu's: 0 4 and 5. But the box has 8 cpu's according to the 'machinfo' command. There are 4 processes using 10% "%CPU" each but it shows the box as 90% idle...??? Also, I don't see any... (16 Replies)
Discussion started by: mj62mj62
16 Replies

4. Programming

locking mutexes, threads & semahores

What is the difference between mutex_lock and pthread_mutex_lock ? Should I use both when using binary semaphores. Also, what is the difference between using a binary semaphore and a counting semaphore where you wait on the condition variable ? (1 Reply)
Discussion started by: joey
1 Replies

5. UNIX for Advanced & Expert Users

Native & Green Threads

Hi, While compiling an application on Solaris 10, I observe the following printout. The same compilation passed some time ago(but perhaps the compilers were different then! We are maintaining this product and lost track of previous changes). ... (1 Reply)
Discussion started by: smanu
1 Replies

6. Solaris

Which company's hardware is more stable, in case of IBM (AIX), HP (HPUX) & Sun (Solaris)

Hi guru I want to know which company's hardware is more stable means in term of H/W faults or replacement, in case of IBM (AIX), HP (HPUX) & SUN MICROSYSTEM (Solaris) & which order also, if we go through more stable to less stable system. Regards (1 Reply)
Discussion started by: girish.batra
1 Replies

7. Programming

Undefined reference to omp_get_thread_num using OpenMP?

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
CPUSET(3)						   BSD Library Functions Manual 						 CPUSET(3)

NAME
cpuset_create, cpuset_destroy, cpuset_zero, cpuset_set, cpuset_clr, cpuset_isset, cpuset_size -- dynamic CPU sets SYNOPSIS
#include <sched.h> cpuset_t * cpuset_create(void); void cpuset_destroy(cpuset_t *set); void cpuset_zero(cpuset_t *set); int cpuset_set(cpuid_t cpu, cpuset_t *set); int cpuset_clr(cpuid_t cpu, cpuset_t *set); int cpuset_isset(cpuid_t cpu, const cpuset_t *set); size_t cpuset_size(const cpuset_t *set); DESCRIPTION
This section describes the functions used to create, set, use and destroy the dynamic CPU sets. This API can be used with the POSIX threads, see pthread(3) and affinity(3). The ID of the primary CPU in the system is 0. FUNCTIONS
cpuset_create() Allocates and initializes a clean CPU-set. Returns the pointer to the CPU-set, or NULL on failure. cpuset_destroy(set) Destroy the CPU-set specified by set. cpuset_zero(set) Makes the CPU-set specified by set clean, that is, memory is initialized to zero bytes, and none of the CPUs set. cpuset_set(cpu, set) Sets the CPU specified by cpu in set. Returns zero on success, and -1 if cpu is invalid. cpuset_clr(cpu, set) Clears the CPU specified by cpu in the CPU-set set. Returns zero on success, and -1 if cpu is invalid. cpuset_isset(cpu, set) Checks if CPU specified by cpu is set in the CPU-set set. Returns the positive number if set, zero if not set, and -1 if cpu is invalid. cpuset_size(set) Returns the size in bytes of CPU-set specified by set. SEE ALSO
affinity(3), pset(3), sched(3), schedctl(8), kcpuset(9) HISTORY
The dynamic CPU sets appeared in NetBSD 5.0. BSD
November 2, 2011 BSD
All times are GMT -4. The time now is 01:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy