Sponsored Content
Full Discussion: CPU/processor/cores in M4000
Operating Systems Solaris CPU/processor/cores in M4000 Post 302905017 by DukeNuke2 on Monday 9th of June 2014 06:22:25 AM
Old 06-09-2014
The SPARC64-VI processor has 2 cores with 2 threads each.

So 4 physical processors are 8 cores and 16 threads.
This User Gave Thanks to DukeNuke2 For This Post:
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Cores on a processor

Hi All, What is the command to identify whether a processor is single core / dual core in solaris ? Thanks. (2 Replies)
Discussion started by: RAA
2 Replies

2. Shell Programming and Scripting

Is there a way to make bash [or another shell] use all CPU cores to execute a single script?

I wrote a very simple script that matches combinations of alphabetic characters (1-5). I want to use it to test CPU speeds of different hardware/platforms. The problem is that on multi-core/processor systems, only one CPU is being utilized to execute the script. Is there a way to change that?... (16 Replies)
Discussion started by: ph0enix
16 Replies

3. Red Hat

Lost CPU CORES

Hey all, dmidecode | grep -i CPU Socket Designation: CPU 0 Version: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz Socket Designation: CPU 1 Version: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz cat /proc/cpuinfo | grep -i cpu cpu family : 6... (24 Replies)
Discussion started by: rmokros
24 Replies

4. UNIX for Dummies Questions & Answers

how to run two unix/linux programs on two different cpu cores

Hi folks, I want to know how to run two unix programs on two different cpu cores on a 2-core or 4-core or 8-core CPU machine? Extending this how would i run four and eight unix programs on 4-core and 8-core machine respectively? If this can be done, how to know which program is assigned to... (1 Reply)
Discussion started by: kaaliakahn
1 Replies

5. Programming

Set Processor Affinity to group of cores

Hi on multi-core system - I know I can set each process to run on specific core (Processor Affinity). If I want to set process (which contains several threads) to run on group of core, how can I do it ? For example: If we have 8 core, and two process each process contain 4 threads. And I... (2 Replies)
Discussion started by: laro1983
2 Replies

6. Solaris

Numbers-of-cpu-cores-in-Solaris-10

Hello All, How do I find the number of CPU's, virtual processors in solaris 10? Thank you Sunil Kumar (2 Replies)
Discussion started by: msgforsunil
2 Replies

7. Red Hat

CPU and Cores information

Hi all. I have a question about linux command to find number of CPU and Core. I usually use the command dmidecode -t processor to find cpu and core numbers . On this machine with Red Hat 4. 0 when I try to insert the command is returned the error -bash: dmidecode: command not found I try to... (8 Replies)
Discussion started by: piccolinomax
8 Replies

8. Solaris

Questions regarding CPU cores vs rctl limit

Hi, I am trying to gather cpu core details and used this script - Solaris & Scripting: Script - Find cpu - model / type / count / core / thread / speed - Solaris Sparc For auuditing purpose, we want to know how many cores are being used by Oracle, because oracle license will be charged on... (2 Replies)
Discussion started by: solaris_1977
2 Replies
pset_getattr(2) 						System Calls Manual						   pset_getattr(2)

NAME
pset_getattr(), pset_setattr() - manage processor set attributes SYNOPSIS
DESCRIPTION
The function returns the current value of the attribute type for the processor set pset in the memory location pointed to by val. The function assigns the value val to the attribute type for processor set pset. A user can not change the attribute values for the system default processor set using the function. A user with the privilege or a user with READ permission for the processor set may query any attribute values. The following processor set attributes may be queried or changed through these functions: The GID (group id) of the processor set owner. The creator's GID is assigned at processor set creation time. A user with the privilege or the pset owner may change the value of this attribute. The UID of the processor set owner. The creator is assigned as the owner at processor set creation time. A user with the privilege or the pset owner may change the value of this attribute. The access permission bitmask for the processor set. These are defined similar to file access permissions. There are three types of access: The user can bind its process or thread to the processor set using the function (see pset_bind(2)). The user can query the processor set attributes. The user can modify the processor set attributes and configuration, and destroy the processor set. The following bit values are used for the access bitmask: All users in processor set owner's group have EXEC access. All users in processor set owner's group have READ access. All users in processor set owner's group have WRITE access. All others have EXEC access. All others have READ access. All others have WRITE access. The processor set owner has EXEC access. The processor set owner has READ access. The processor set owner has WRITE access. A newly created processor set by default has READ and EXEC access for everyone, but WRITE access only for the processor set owner. A user with the privilege or the pset owner may change the value of the attribute. A value of indicates that processors in this processor set are configured to receive external interrupts. It may be assigned a value of to disable all processors in the processor set from receiving and processing external I/O interrupts. Not all platforms may support this feature. By default, I/O interrupts are enabled on all processors. The feature may be useful for some realtime applica- tions where unpredictable interrupt handling overhead may adversely impact the application's response time requirements. Only a user with the privilege may change this attribute. Indicates the behavior when a request to destroy a non-empty processor set is made through the function. Possible values are: Reassign all processors in the processor set pset to the system default processor set. Migrate all threads and processes bound to this processor set to the system default processor set. This is the default value for this attribute. Make the request fail with an error if there are threads or processes bound to the processor set or if there are processors assigned to the processor set. Make the request fail with an error if there are active threads or processes bound to the processor set. Otherwise, perform the operation by reas- signing the processors in the pset to the system default processor set. A user with the privilege or a user with WRITE permissions may change the value of this attribute. Indicates the behavior when a request to bind a process or a thread to an empty processor set is made through the function. Possible values are: Go through with the request. However, the affected threads will not be scheduled to execute until a processor is assigned to the empty processor set. Reject the request with an error. This is the default value for this attribute. A user with the privilege or a user with WRITE permissions may change the value of this attribute. Indicates the behavior when a request to remove the last processor from a processor set is made through the function, or through the processor deallocation functionality. Possible values are: Make the request fail if there are active threads and processes assigned to the processor set. Assign the processor to the specified processor set, and migrate all threads and processes to the system default processor set This is the default value for this attribute. A user with the privilege or a user with WRITE permissions may change the value of the attribute. The LCPU attribute of a processor set indicates whether the physical processor cores in a pset are enabled with logical processors (LCPUs). On systems with the Hyper-Threading (HT) feature enabled, each proces- sor 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). The can be set for the default processor set using the command. This attribute is supported only on system with the Hyper-Threading feature. If this feature is disabled at the firmware level or is not supported, this attribute cannot change. Enable the LCPUs in a processor set. This is the default value for systems with the Hyper-Threading feature enabled. Disable the LCPUs in the processor set. This is the default value for the systems without the Hyper-Threading feature or systems with the Hyper-Threading disabled in the firmware. The default value for any attribute can be assigned using the value in the function. 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. RETURN VALUE
The functions return zero on successful completion. Otherwise, -1 is returned and errno is set to indicate the error. ERRORS
or fails if one or more of the following is true: The memory location pointed to by val is not writable by the user for The specified processor set pset, the attribute type, or the attribute val is invalid. The memory location pointed to by val is NULL for The processor set functionality is not supported by the underlying HP-UX version. The requested attribute value is not supported for the function. The user does not have the necessary permissions to query or change the processor set attributes. AUTHOR
and were developed by HP. SEE ALSO
kctune(1M), psrset(1M), pset_assign(2), pset_bind(2), pset_create(2), pset_ctl(2), pset_destroy(2), privgrp(4), lcpu_attr(5), privi- leges(5). pset_getattr(2)
All times are GMT -4. The time now is 07:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy