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.

• New macros to allow for simple read-write locking, and the INIFADDR lock<br />

macros are changed to use them.<br />

7.9.3.2 Reducing the Contention of Route Lock<br />

Currently, all outgoing IP packets must take the single route lock. On an SMP<br />

machine with multiple adapters, a large number of packets must take this lock, so<br />

it is the hot (critical) lock on output. Reducing the contention on this lock can<br />

increase the throughput on SMP systems with multiple adapters.<br />

There is a global route lock that must be taken any time any route is changed or<br />

used. Each connection keeps a pointer to a cached route, but it still must take the<br />

route lock to check the validity of its cached route. So, the route lock must be<br />

taken for every outgoing packet.<br />

The new design eliminates the requirement to take the global route lock for<br />

outgoing packets in the case where the cached route is valid. This should<br />

improve performance for TCP, where the cached route will usually be valid so the<br />

global lock will not be needed on packet output. For UDP, the cached route often<br />

is not valid, and so the global lock will still be needed for output. But since the<br />

contention on this lock from other code will be reduced, there is also a<br />

performance improvement for UDP.<br />

The global route lock that protects the structure of the routing table has also been<br />

changed to use the same read/write lock in places where the global lock is still<br />

needed.<br />

7.10 TCP Checksum Offload on ATM 155 Mbps PCI Adapter (<strong>4.3</strong>.2)<br />

The PCI ATM 155 adapter has a hardware TCP/UDP checksum capability. In <strong>AIX</strong><br />

<strong>4.3</strong>.2, the ATM network device driver is modified to use this feature.<br />

In the new ATM 155 adapter device driver, the workload of TCP data checksum<br />

processing is offloaded from the <strong>AIX</strong> TCP/IP protocol stack to the adapter itself. A<br />

related enhancement automatically remembers the mapping of virtual addresses<br />

to physical addresses for the entire networking buffer pool to save address<br />

translation during networking I/O operations.<br />

TCP checksum offload for ATM reduces the amount of time spent on the main<br />

CPU computing checksums, thereby reducing latency and allowing the system to<br />

handle more work, in particular, to handle more packets in the same amount of<br />

time. This results in performance improvements.<br />

The SpecWeb96 benchmark is published on the 7017-S70 using ATM interfaces.<br />

It benefits from this checksum offload capability.<br />

TCP and the other network layers continue to perform as they do today,<br />

particularly on adapters that do not support checksum offload. All TCP functions<br />

are the same.<br />

In order to improve performance for TCP over ATM, small packets do not have<br />

their checksum processing offloaded since setting up the offload will probably use<br />

as much processor time as computing the checksum. There is no gain, and may<br />

actually be a loss, in offloading checksum processing for these small packets.<br />

176 <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!