- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Process priority influenced by param.h?
Operating System - HP-UX
1753677
Members
5537
Online
108799
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
тАО06-30-2003 11:06 PM
тАО06-30-2003 11:06 PM
Process priority influenced by param.h?
We have processes running at priority 152, eating cpu as hell. As far as I can notice, the priority of those processes doesn't change, even with a nice value of 39. When I look into /usr/include/sys/param.h, I find something that (maybe) could influence the base priority of a process ie. PRIBETA (6+PTIMESHARE) PUSER (50+PTIMESHARE) and so on. This latter gives a (base) priority PUSER of 178 or the normal priority of a process. Are those definitions indeed base priorities? And if so, how can we assign a base priority to a process?
JJFRAN
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2004 10:33 PM
тАО10-27-2004 10:33 PM
Re: Process priority influenced by param.h?
Hi jos,
I am also looking for something like this. Did you able to solve this issue.
Can u provide in more details on this?
Many Thanks
I am also looking for something like this. Did you able to solve this issue.
Can u provide in more details on this?
Many Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-12-2004 10:34 PM
тАО12-12-2004 10:34 PM
Re: Process priority influenced by param.h?
Real time priority values (0 - 127) are reserved for processes started using a rtprio() call and are used in a real-time scheduling policy.
System priority values (128 - 177) are used in a time-sharing scheduling policy.
User priority values (178 - 255) are used in a time-sharing scheduling policy.
The kernel can change the priority of any process within a time-sharing scheduling policy, but it can't change the priority of a real-time process.
Thus if a process is running with a priority of 152, it must be a system priority value rather than a user one (the default). The kernel believes that the process is running on behalf of the system, rather than as a user's process. e.g. vxfsd will typically have a priority of 152.
System priority values (128 - 177) are used in a time-sharing scheduling policy.
User priority values (178 - 255) are used in a time-sharing scheduling policy.
The kernel can change the priority of any process within a time-sharing scheduling policy, but it can't change the priority of a real-time process.
Thus if a process is running with a priority of 152, it must be a system priority value rather than a user one (the default). The kernel believes that the process is running on behalf of the system, rather than as a user's process. e.g. vxfsd will typically have a priority of 152.
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