Sponsored Content
Operating Systems HP-UX Multicore from a different angle Post 92251 by Midcain on Thursday 8th of December 2005 05:30:17 PM
Old 12-08-2005
I have to be able to do this programmatically, Eronysis. On single-core and dual-core systems, which breaks the division idea . . . unless I want to report half a processor.
 

4 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Angle brackets

From the Apache thread in the Adanced forum: Thats because your browser interprets anything within angle brackets to be an HTML tag. You need to quote these brackets if you want them to appear correctly. The proper quotes are: &amp;lt; for < and &amp;gt; for > So, for example, you would have... (1 Reply)
Discussion started by: PxT
1 Replies

2. Post Here to Contact Site Administrators and Moderators

angle brackets should be escaped automatically

I think that HTML code within posts should be turned off -- the vB Code can provide all the features we need. Then, you should modify the program to automatically escape any angle brackets, so that &lt; gets translated to &amp;lt; and &gt; gets translated to &amp;gt; I see a lot of people garble their posts... (4 Replies)
Discussion started by: PxT
4 Replies

3. HP-UX

How do I detect multicore processors?

I'm fairly new to HP-UX, and I need to know how to identify the number of cores on a PA-8800 processor from the command line. Any help here would be appreciated. (11 Replies)
Discussion started by: Midcain
11 Replies

4. Shell Programming and Scripting

How give tasks to individual processors in a multicore processor ?

Hi all, Using shell script, how to assign tasks to individual processors in a multicore processor ? For example: If I have 4 processors, I want to give one job to each of the processors. (When I give multiple jobs, it's assigning all the load to a single processor. ) Thanks R (5 Replies)
Discussion started by: habzone2007
5 Replies
pset_destroy(2) 						System Calls Manual						   pset_destroy(2)

NAME
pset_destroy() - destroy a processor set SYNOPSIS
DESCRIPTION
The function destroys the processor set pset, releasing all constituent processors and processes by default. The processors and processes are reassigned to the system default processor set. Once destroyed, the pset identifier becomes available for new processor sets that may be created in the future. The behavior when attempting to destroy a non-empty processor set may be controlled by changing the attribute of the processor set through the function. See pset_getattr(2). The following values are supported for the attribute: Reassign all processors in the pset to the system default processor set. Migrate all threads and processes bound to the pset to the system default proces- sor set. Make the request fail with if there are any threads or processes bound to pset or if there are processors assigned to the pset. Make the request fail with only if there are active threads or processes bound to the processor set. Otherwise, perform the operation by reassigning the processors in the pset to the system default processor set. If the threads and processes being reassigned to the default processor set have some binding to a processor or a locality domain in the pset being destroyed, their binding is reassigned to a processor or a locality domain in the system default processor set. A user with the privilege or a user with WRITE permission on the pset may destroy the processor set pset. The system default processor set may never be destroyed. Security Restrictions Some or all of the actions associated with this system call require the privilege. Processes owned by the superuser have this privilege. Processes owned by other users may have this privilege, depending on system configuration. See privileges(5) for more information about privileged access on systems that support fine-grained privileges. Note on Logical Processor and Hyper-Threading Feature On systems with the Hyper-Threading (HT) feature enabled at the firmware level, each processor core may have more than one hyper-thread per physical processor core. Each hyper-thread is represented to the operating system and applications as a logical processor (LCPU). Due to the processor set contract, which specifies that applications bound to a processor set have complete and exclusive control of all processor cores within that processor set, migration of processors between two processor sets is done at the processor core granularity. For destruction of a processor set migrates a set of processor cores to the default processor set. Depending on the source processor set and the default processor set's the number of logical processors visible to the users and applications may change. EXAMPLES
Destroy a processor set with the processor set ID of pset. RETURN VALUE
returns zero on successful completion. Otherwise, -1 is returned and is set to indicate the error. ERRORS
fails if one or more of the following is true: The attribute value for the processor set does not allow deletion of a non-empty processor set. The operation was interrupted. pset is not a valid processor set. The processor set functionality is not supported by the underlying HP-UX version. The user does not have necessary permissions to destroy a processor set or the system default processor set was specified. SEE ALSO
psrset(1M), pset_assign(2), pset_bind(2), pset_create(2), pset_ctl(2), pset_getattr(2), privgrp(4), privileges(5). pset_destroy(2)
All times are GMT -4. The time now is 12:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy