From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: Wrong TCP Checkum computed by hardware Date: Tue, 27 Oct 2015 23:57:57 -0700 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 Cc: "dev@dpdk.org" To: Padam Jeet Singh 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) Content-Disposition: inline In-Reply-To: <9E9D668A-17B5-4047-85B3-13519F898467@inventum.net> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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.