24.05.2014 Views

AIX Version 4.3 Differences Guide

AIX Version 4.3 Differences Guide

AIX Version 4.3 Differences Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

• Debugging purposes. These trace points are only enabled when the driver is<br />

compiled with -DDEBUG turned on, and therefore, the driver can contain as<br />

many of these trace points as desired.<br />

The main goals for having trace points in a CDLI device driver are to be able to<br />

monitor drivers for errors and to track packets as they move through the driver. To<br />

this end, it is important that trace points be placed at the beginning and end of<br />

each main routine that does processing on packets. Also, it is important to try and<br />

trace the flow of buffers (for example, mbufs) as they flow through the system.<br />

There should also be trace points placed at each point where an error could<br />

occur.<br />

The device driver also has trace points to support the netpmon program<br />

(component cmdperft). There are generally five trace points:<br />

WQUE An output packet has been queued for transmission.<br />

WEND The output of a packet is complete.<br />

RDAT An input packet has been received by the device driver.<br />

RNOT An input packet has been given to the demuxer.<br />

REND The demuxer has returned.<br />

All CDLI drivers must register for a trace hook IDs.<br />

NOTE: CDLI device drivers may register for more than one trace hook ID. In the<br />

case of multiple trace hook IDs, one could be used for transmit, one for receive,<br />

and another for errors.<br />

7.13.3 Error Logging<br />

The device driver will do error logging when the following situations occur:<br />

• An error on PIO operations<br />

• A hardware failure on the device<br />

• An error on DMA operations<br />

• Network errors<br />

• Other device specific errors<br />

7.14 Open Network Computing (ONC+)<br />

The ONC+ technology has been licensed from SunSoft and is being included<br />

within <strong>AIX</strong> to meet customer requirements. This technology contains many<br />

different functional components; the main ones being: NFS <strong>Version</strong> 3, NIS+,<br />

CacheFS, TIRPC, and AutoFS. Not all of these components are included with this<br />

release of <strong>AIX</strong>. NFS V3 was introduced in <strong>AIX</strong> <strong>Version</strong> 4.2.1. CacheFS was<br />

introduced in <strong>AIX</strong> <strong>Version</strong> <strong>4.3</strong>.0, and AutoFS was included in <strong>AIX</strong> <strong>4.3</strong>.1.<br />

7.14.1 CacheFS<br />

CacheFS is a local disk cache mechanism for NFS clients. It provides the ability<br />

for an NFS client to cache file system data on its local disk, thereby avoiding use<br />

of the network and NFS server when the data is accessed and is not in physical<br />

memory. This improves NFS server performance and scalability by reducing<br />

182 <strong>AIX</strong> <strong>Version</strong> <strong>4.3</strong> <strong>Differences</strong> <strong>Guide</strong>

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

Saved successfully!

Ooh no, something went wrong!