公开(公告)号：CA2548966C

公开(公告)日：2010-06-01

申请号：CA2548966

申请日：2004-12-06

Applicant: IBM

Inventor： MAKHER-VAKS VADIM ,  MACHULSKY ZORIK ,  BIRAN GIORA ,  SHALEV LEAH

IPC: H04L29/08 ,  G06F15/16 ,  H04L29/06

Abstract: An RNIC implementation that performs direct data placement to memory where all segments of a particular connection are aligned, or moves data through reassembly buffers where all segments of a particular connection are non-aligned. The type of connection that cuts-through without accessing the reassembly buffers is referred to as a "Fast" connection because it is highly likely to be aligned, while the other type is referred to as a "Slow" connection. When a consumer establishes a connection, it specifies a connection type (S2). The connection type can change from Fast to Slow and back. The invention reduces memory bandwidth, latency, error recovery using TCP retransmit and provides for a "graceful recovery" from an empty receive queue. The implementation also may conduct CRC validation (S11, S6) for a majority of inbound DDP segments in the Fast connection before sending a TCP acknowledgement (Ack) confirming segment reception.

公开(公告)号：CA2548966A1

公开(公告)日：2005-07-07

申请号：CA2548966

申请日：2004-12-06

Applicant: IBM

Inventor： MAKHER-VAKS VADIM ,  MACHULSKY ZORIK ,  BIRAN GIORA ,  SHALEV LEAH

IPC: G06F15/16 ,  H04L29/06

Abstract: An RNIC implementation that performs direct data placement to memory where a ll segments of a particular connection are aligned, or moves data through reassembly buffers where all segments of a particular connection are non- aligned. The type of connection that cuts-through without accessing the reassembly buffers is referred to as a "Fast" connection because it is highl y likely to be aligned, while the other type is referred to as a "Slow" connection. When a consumer establishes a connection, it specifies a connection type (S2). The connection type can change from Fast to Slow and back. The invention reduces memory bandwidth, latency, error recovery using TCP retransmit and provides for a "graceful recovery" from an empty receive queue. The implementation also may conduct CRC validation (S11, S6) for a majority of inbound DDP segments in the Fast connection before sending a TCP acknowledgement (Ack) confirming segment reception.