21.02.2013 Views

AIX 5L Problem Determination - IBM Redbooks

AIX 5L Problem Determination - IBM Redbooks

AIX 5L Problem Determination - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

process belongs to (when not shared, or shared by processes in the same<br />

superclass) or to the Shared superclass, when shared by processes in<br />

different superclasses. However, there are a few pages that cannot be<br />

directly tied to any processes (and thus to any class) at the time of this<br />

classification, and this memory is charged to the Unclassified superclass; for<br />

example, pages from a file that has been closed. The file pages will remain in<br />

memory, but no process owns these pages; therefore, they cannot be<br />

charged to a specific class. Most of this memory will end up being correctly<br />

reclassified over time, when it is either accessed by a process, or freed and<br />

reallocated to a process after WLM is started. There are a few kernel<br />

processes, such as wait or Irud, in the Unclassified superclass. Even though<br />

this superclass can have physical memory shares and limits applied to it,<br />

WLM commands do not allow you to set shares and limits or specify<br />

subclasses or assignment rules on this superclass.<br />

► Unmanaged superclass: A special superclass named Unmanaged will always<br />

be defined. No processes will be assigned to this class. This class will be<br />

used to accumulate the memory usage for all pinned pages in the system that<br />

are not managed by WLM. The CPU utilization for the waitprocs is not<br />

accumulated in any class. This is deliberate; otherwise, the system would<br />

always seem to be at 100 percent CPU utilization, which could be misleading<br />

for users when looking at the WLM or system statistics. This superclass<br />

cannot have shares or limits for any other resource types, subclasses, or<br />

assignment rules specified.<br />

Subclasses<br />

A subclass is a class associated with exactly one superclass. Every process in<br />

the subclass is also a member of the superclass. Subclasses only have access<br />

to resources that are available to the superclass. A subclass has a set of class<br />

assignment rules that determine which of the processes assigned to the<br />

superclass will belong to it. A subclass also has a set of resource limitation<br />

values and resource target shares that determine the resources that can be used<br />

by processes in the subclass. These resource limitation values and resource<br />

target shares indicate how much of the superclass’s target (the resources<br />

available to the superclass) can be used by processes in the subclass.<br />

Up to 10 out of a total of 12 subclasses can be defined by the system<br />

administrator or by the superclass administrator for each superclass. In addition,<br />

two special subclasses, Default and Shared, are always defined in each<br />

superclass as follows:<br />

► Default subclass: The default subclass is named Default and is always<br />

defined. All processes that are not automatically assigned to a specific<br />

subclass of the superclass will be assigned to the Default subclass. You can<br />

also assign other processes to the Default subclass by providing specific<br />

assignment rules.<br />

Chapter 10. Performance problem determination 279

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!