From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id C0DE68D9F for ; Wed, 28 Oct 2015 07:59:43 +0100 (CET) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 38DDE80C502; Tue, 27 Oct 2015 23:57:57 -0700 (PDT) Date: Tue, 27 Oct 2015 23:57:57 -0700 From: Matthew Hall To: Padam Jeet Singh Message-ID: <20151028065757.GA4251@mhcomputing.net> References: <9E9D668A-17B5-4047-85B3-13519F898467@inventum.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9E9D668A-17B5-4047-85B3-13519F898467@inventum.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Wrong TCP Checkum computed by hardware X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Oct 2015 06:59:44 -0000 On Wed, Oct 28, 2015 at 12:20:22PM +0530, Padam Jeet Singh wrote: > Any hint what could I be doing wrong here? When this kind of stuff doesn't work it often will depend on the exact version of card, chip, etc. if there are any errata. So you might want to collect the specifics of the board with lspci -v, ethtool, and pulling it out to check the chip and board revisions. In addition check over the example apps and see how things work there compared with your own code. Often the DPDK interfaces are kind of complex and small pointer or mbuf manipulation mistakes can cause very odd results. Matthew.