Return-Path: X-Sieve: cmu-sieve 2.0 Return-Path: Received: (from majordom@localhost) by ece.cmu.edu (8.11.0/8.10.2) id h0NNZGI01481 for ips-outgoing; Thu, 23 Jan 2003 18:35:16 -0500 (EST) X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f Received: from marantinetworks.com (66-147-154-67.focaldata.net [66.147.154.67] (may be forged)) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h0NNZDW01472 for ; Thu, 23 Jan 2003 18:35:13 -0500 (EST) Received: from Pverma (Sonic.marantinetworks.com [66.147.154.66]) by marantinetworks.com (8.11.2/8.11.2) with SMTP id h0NNXet17015 for ; Thu, 23 Jan 2003 15:33:40 -0800 Reply-To: From: "Preetam Verma" To: Subject: How to handle CRC errors? Date: Thu, 23 Jan 2003 15:32:24 -0800 Message-ID: <006201c2c337$af63dc10$b6000a0a@maranti.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-ips@ece.cmu.edu Precedence: bulk I have a situation like this: CPU | | <---------------->port<---------->TCP offload engine <------------->Logic<----------------->Application processing The logic is going to assemble PDUs and pass them on to the application. If a PDU that came in has CRC errors, will the application need to signal the initiator to terminate the session? Say a PDU header from the TCP offload engine was corrupted, how would the "logic" need to handle the data that comes later. How do I ensure that the application receives packets in order? How can I ensure that in such an event the PDU processing logic does not go out of sync? Regards Preetam