This morning, I checked the Exception Letters for our z9 and z10 processors.  
Both Exception Letters are dated May 28, 2008, and both still say that 
Segmentation Offload needs to be disabled.

I am not saying that IBM hasn't fixed the problem - I hope they have.  But, 
the Exception Letters still say the problem is NOT fixed.

FYI - the Exception Letters are found in ResourceLink by clicking on Fixes, and 
then Exception Letters.

Brian

On Wed, 4 Jun 2008 12:57:52 -0500, Chase, John wrote:

>Forwarded on behalf of a colleague.......
>
>
>________________________________
>
>       IBM recommended a while back that TCP/IP Segmentation Offload to
>the OSA card be disabled.  Microcode was made available in April to fix
>the offload code.  We are now at this new microcode level and are
>considering re-enabling the offload functionality.   We are aware of
>APAR PK64756. 
>        
>       Has anyone experienced any problems after re-enabling
>Segmentation Offload?
>        
>       Any recommendations on the best way to measure the positive
>performance impact that segmentation offload provides to TCP/IP (CPU,
>storage, etc.)?
>
>TIA,
> 
>    -jc-
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to