- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: how to set a processor
Operating System - Tru64 Unix
1747997
Members
4457
Online
108756
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2004 02:04 AM
тАО12-09-2004 02:04 AM
Re: how to set a processor
Sorry I meant to say SRM (not SRN) in my prev post....
Here is what this cpu_enabled SRM variable is all about...
To disable one or more cpus at the console level, you change the setting of the
"cpu_enabled" console environment variable. The variable is essentially a bit
vector with one bit for each cpu. The default value is to have all cpus enabled
(that is, all the bits of the bit vector are set to "1"). To disable a cpu, you
need to set the corresponding bit to zero and then execute the "init" command or
power cycle the system.
A bit of explanation about the "cpu_enabled" variable:
For a system that can be configured with up to 4 cpus, the corresponding bit
vector of that system's "cpu_enabled" variable has 4 bits:
1 1 1 1
cpu 3 2 1 0
and they are all set to 1s therefore the corresponding value of the
"cpu_enabled" variable is F (hexadecimal).
If you wanted to disable CPU 2 for instance, you would change the bit vector
thus:
1 0 1 1
cpu 3 2 1 0
by setting the "cpu_enabled" console variable to A (hexadecimal). This you do
by entering the command "set cpu_enabled A" at the console (">>>") prompt.
CPU0 is always enabled. Even if you set cpu_enabled to 0 CPU0 is still enabled.
If you set cpu_enabled to 2 -- both CPU0 & CPU1 are enabled (as if it was set to 3).
HTH,
Ross
Here is what this cpu_enabled SRM variable is all about...
To disable one or more cpus at the console level, you change the setting of the
"cpu_enabled" console environment variable. The variable is essentially a bit
vector with one bit for each cpu. The default value is to have all cpus enabled
(that is, all the bits of the bit vector are set to "1"). To disable a cpu, you
need to set the corresponding bit to zero and then execute the "init" command or
power cycle the system.
A bit of explanation about the "cpu_enabled" variable:
For a system that can be configured with up to 4 cpus, the corresponding bit
vector of that system's "cpu_enabled" variable has 4 bits:
1 1 1 1
cpu 3 2 1 0
and they are all set to 1s therefore the corresponding value of the
"cpu_enabled" variable is F (hexadecimal).
If you wanted to disable CPU 2 for instance, you would change the bit vector
thus:
1 0 1 1
cpu 3 2 1 0
by setting the "cpu_enabled" console variable to A (hexadecimal). This you do
by entering the command "set cpu_enabled A" at the console (">>>") prompt.
CPU0 is always enabled. Even if you set cpu_enabled to 0 CPU0 is still enabled.
If you set cpu_enabled to 2 -- both CPU0 & CPU1 are enabled (as if it was set to 3).
HTH,
Ross
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2004 02:59 AM
тАО12-09-2004 02:59 AM
Re: how to set a processor
Wahyono,
Please help us help you by giving us concrete and exact data to work with.
- pset_info output
- psrinfo output
>> if i use 'psradm', it says 'permission denied (login using root).
What are you asking psradm to do? Is the processor actually there? (psrinfo!)
>> i haven't tried other options, cause it's in the running system...i have to consider the impact
Well... making pset's effectively takes the assigned cpu completely away from the running systems. That's about the niggest impact you can make!
The 'runon' + renice suggestion has just about no side impact.
Good luck,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2004 12:23 PM
тАО12-09-2004 12:23 PM
Re: how to set a processor
Guys,
these are the outputs of some commands.
i really appreciate your help
rgrds
Wahyono
these are the outputs of some commands.
i really appreciate your help
rgrds
Wahyono
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2004 05:01 PM
тАО12-09-2004 05:01 PM
Re: how to set a processor
Thanks for that listing.
It shows somethign 'odd'
There is a line missing for cpu# 1 in:
-----------
cpu # running primary_cpu pset_id assigned_to_pset
0 1 1 0 11/26/2004 11:07:58
------------
It is my understanding that if cpu# 1 was not in any pset, it would be reported as pset -1
Here is how it works on my test system:
# uname -a OSF1 kelrin V5.1 2650 alpha
# pset_create
pset_id = 2
# pset_assign_cpu 2 2
# pset_info
number of processor sets on system = 2
pset_id # cpus # pids # threads load_av created
0 3 69 277 0.00 11/18/2004 13:42:28
2 1 0 0 0.00 12/10/2004 00:55:22
total number of processors on system = 4
cpu # running primary_cpu pset_id assigned_to_pset
0 1 1 0 11/18/2004 13:42:28
1 1 0 0 11/18/2004 13:42:28
2 1 0 2 12/10/2004 00:55:40
3 1 0 0 11/18/2004 13:42:28
# pset_destroy 2
processor set 2 has active processors/tasks/threads assigned to it.
destroy anyway? (y/n): y
# pset_info
number of processor sets on system = 1
pset_id # cpus # pids # threads load_av created
0 4 69 277 0.00 11/18/2004 13:42:28
total number of processors on system = 4
cpu # running primary_cpu pset_id assigned_to_pset
0 1 1 0 11/18/2004 13:42:28
1 1 0 0 11/18/2004 13:42:28
2 1 0 0 12/10/2004 00:56:32
3 1 0 0 11/18/2004 13:42:28
#
You may have found a bug,
Or just an unfortunate series of trail.
Hate to say this, but I would try again after a reboot at your earliest convenience.
In the mean time, assuming CPU #1 is actively used and not wasted (top or monitor?) I woudl continue on and see if runon/renice can address your needs without psets
Hein.
It shows somethign 'odd'
There is a line missing for cpu# 1 in:
-----------
cpu # running primary_cpu pset_id assigned_to_pset
0 1 1 0 11/26/2004 11:07:58
------------
It is my understanding that if cpu# 1 was not in any pset, it would be reported as pset -1
Here is how it works on my test system:
# uname -a OSF1 kelrin V5.1 2650 alpha
# pset_create
pset_id = 2
# pset_assign_cpu 2 2
# pset_info
number of processor sets on system = 2
pset_id # cpus # pids # threads load_av created
0 3 69 277 0.00 11/18/2004 13:42:28
2 1 0 0 0.00 12/10/2004 00:55:22
total number of processors on system = 4
cpu # running primary_cpu pset_id assigned_to_pset
0 1 1 0 11/18/2004 13:42:28
1 1 0 0 11/18/2004 13:42:28
2 1 0 2 12/10/2004 00:55:40
3 1 0 0 11/18/2004 13:42:28
# pset_destroy 2
processor set 2 has active processors/tasks/threads assigned to it.
destroy anyway? (y/n): y
# pset_info
number of processor sets on system = 1
pset_id # cpus # pids # threads load_av created
0 4 69 277 0.00 11/18/2004 13:42:28
total number of processors on system = 4
cpu # running primary_cpu pset_id assigned_to_pset
0 1 1 0 11/18/2004 13:42:28
1 1 0 0 11/18/2004 13:42:28
2 1 0 0 12/10/2004 00:56:32
3 1 0 0 11/18/2004 13:42:28
#
You may have found a bug,
Or just an unfortunate series of trail.
Hate to say this, but I would try again after a reboot at your earliest convenience.
In the mean time, assuming CPU #1 is actively used and not wasted (top or monitor?) I woudl continue on and see if runon/renice can address your needs without psets
Hein.
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP