- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Help! What is the daemon named "netisr"?Which eat ...
Operating System - HP-UX
1752686
Members
5509
Online
108789
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-21-2001 11:27 PM
тАО06-21-2001 11:27 PM
Help! What is the daemon named "netisr"?Which eat so much CPU?
Load averages: 17.83, 13.92, 11.56
1074 processes: 1072 sleeping, 2 running
Cpu states:
CPU LOAD USER NICE SYS IDLE BLOCK SWAIT INTR SSYS
0 15.81 3.5% 0.0% 31.4% 65.1% 0.0% 0.0% 0.0% 0.0%
1 19.85 7.5% 0.0% 39.5% 53.0% 0.0% 0.0% 0.0% 0.0%
--- ---- - - - - - - - -----
avg 17.83 5.4% 0.0% 35.5% 59.2% 0.0% 0.0% 0.0% 0.0%
Memory: 730472K (372100K) real, 850024K (359740K) virtual, 19784K free Page# 1/
98
CPU TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
1 rroot 20 root 100 20 0K 0K sleep 1213:27 5.81 5.80 netisr
1074 processes: 1072 sleeping, 2 running
Cpu states:
CPU LOAD USER NICE SYS IDLE BLOCK SWAIT INTR SSYS
0 15.81 3.5% 0.0% 31.4% 65.1% 0.0% 0.0% 0.0% 0.0%
1 19.85 7.5% 0.0% 39.5% 53.0% 0.0% 0.0% 0.0% 0.0%
--- ---- - - - - - - - -----
avg 17.83 5.4% 0.0% 35.5% 59.2% 0.0% 0.0% 0.0% 0.0%
Memory: 730472K (372100K) real, 850024K (359740K) virtual, 19784K free Page# 1/
98
CPU TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
1 rroot 20 root 100 20 0K 0K sleep 1213:27 5.81 5.80 netisr
Always UNIX
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2001 11:52 PM
тАО06-21-2001 11:52 PM
Re: Help! What is the daemon named "netisr"?Which eat so much CPU?
High netisr is symptomatic of a problem somewhere else, ie on the network, in
the TCP/IP stack, the application, or with disk access. On a busy system,
netisr of 80% is quite acceptable, but it is usually a good idea to start
looking for bottlenecks if netisr goes above 30%. A brief explanation of
netisr follows:
"Whenever a network packet arrives the lan card sends an interrupt to
it's CPU. The interrupt routine checks if the packet is valid and
puts it onto the ip_intrqueue. The last thing the interrupt routine
does is to wakeup the netisr to process the packet. If you have a lot
of loopback traffic, all netisr are woken up to process the packets.
The netisr finishes work, when no packet is left on the ip_intrqueue."
To clear netisr down, reboot the system, but you will probably only remove the
symptom and not the problem. A better way is to stop the running applications
one at a time until netisr starts to drop again. A high level of loopback
traffic in netstat -rn usually indicates an application or routing issue.
the TCP/IP stack, the application, or with disk access. On a busy system,
netisr of 80% is quite acceptable, but it is usually a good idea to start
looking for bottlenecks if netisr goes above 30%. A brief explanation of
netisr follows:
"Whenever a network packet arrives the lan card sends an interrupt to
it's CPU. The interrupt routine checks if the packet is valid and
puts it onto the ip_intrqueue. The last thing the interrupt routine
does is to wakeup the netisr to process the packet. If you have a lot
of loopback traffic, all netisr are woken up to process the packets.
The netisr finishes work, when no packet is left on the ip_intrqueue."
To clear netisr down, reboot the system, but you will probably only remove the
symptom and not the problem. A better way is to stop the running applications
one at a time until netisr starts to drop again. A high level of loopback
traffic in netstat -rn usually indicates an application or routing issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-22-2001 12:08 AM
тАО06-22-2001 12:08 AM
Re: Help! What is the daemon named "netisr"?Which eat so much CPU?
# netstat -rn
Routing tables
Destination Gateway Flags Refs Use Interface Pmtu PmtuTime
127.0.0.1 127.0.0.1 UH 8 103260 lo0 4608
x.x.x.x 127.0.0.1 UH 3893912339 lo0 4608
default x.x.x.x UG 3 1897251 lan0 1500
x.x.x.x x.x.x.x U 461872090862 lan0 1500
Routing tables
Destination Gateway Flags Refs Use Interface Pmtu PmtuTime
127.0.0.1 127.0.0.1 UH 8 103260 lo0 4608
x.x.x.x 127.0.0.1 UH 3893912339 lo0 4608
default x.x.x.x UG 3 1897251 lan0 1500
x.x.x.x x.x.x.x U 461872090862 lan0 1500
Always UNIX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-22-2001 02:37 AM
тАО06-22-2001 02:37 AM
Re: Help! What is the daemon named "netisr"?Which eat so much CPU?
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