You should have 5 gil threads on your system. gil = "General ISR List" where ISR = "Interrupt Service Routine." The gil threads handle lots of Streams code and also handle TCP's slow and fast timer routines, amongst other things.
Every 200ms, and every 500ms, the gil thread is kicked off to go run TCP/IP protocol timers (retransmission, delayed acks, etc.).
Normally, it doesn't actually use a lot of CPU time. However, its wakeup points tend to naturally co-incide with the points at which the scheduler collections information associated with CPU load. If you do an 'uptime',you'll see that it usually sits at about 1 even on an idle system. This is the gil thread.
In AIX 3, the work that the gil thread does was done on an offlevel interrupt handler, and was not apparent. In AIX 4, this was moved to a kproc to promote concurrency and SMP scalability.
How do we know that what cuasing the "gil" process to be the toplevel process when we doa topas command. The reason is when "gil" is at top the node is extremely slow i mean it's dead slow. I'm trying to find out waht's causing this slowness.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.