From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <keith.wiles@intel.com>
Received: from mga01.intel.com (mga01.intel.com [192.55.52.88])
 by dpdk.org (Postfix) with ESMTP id B96A710CC9
 for <users@dpdk.org>; Wed, 21 Dec 2016 23:14:34 +0100 (CET)
Received: from fmsmga005.fm.intel.com ([10.253.24.32])
 by fmsmga101.fm.intel.com with ESMTP; 21 Dec 2016 14:14:33 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.33,385,1477983600"; d="scan'208";a="45546720"
Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201])
 by fmsmga005.fm.intel.com with ESMTP; 21 Dec 2016 14:14:33 -0800
Received: from fmsmsx112.amr.corp.intel.com (10.18.116.6) by
 FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Wed, 21 Dec 2016 14:14:33 -0800
Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.68]) by
 FMSMSX112.amr.corp.intel.com ([10.18.116.6]) with mapi id 14.03.0248.002;
 Wed, 21 Dec 2016 14:14:33 -0800
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Kumaraparameshwaran Rathnavel <krath@cloudsimple.com>
CC: "users@dpdk.org" <users@dpdk.org>
Thread-Topic: [dpdk-users] Network Drivers
Thread-Index: AQHSW6niO321AeVgwEGzTEcJGjX55qETff4A
Date: Wed, 21 Dec 2016 22:14:32 +0000
Message-ID: <4F04B62A-306E-44A4-A1FC-0B7B9BF21585@intel.com>
References: <91B0B366-92CD-4257-B082-1623B01DE5DE@cloudsimple.com>
In-Reply-To: <91B0B366-92CD-4257-B082-1623B01DE5DE@cloudsimple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.254.112.141]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D95B38722C283C4B852F5E1F4FA0B97C@intel.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-users] Network Drivers
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Dec 2016 22:14:36 -0000


> On Dec 21, 2016, at 10:46 AM, Kumaraparameshwaran Rathnavel <krath@clouds=
imple.com> wrote:
>=20
> Hi All,
>=20
> When I use the network Drivers provided by the API is the CRC error check=
ing done by the hardware. Or is to be taken care by the software. I do not =
see any of the example APIs doing . So I just wanted to ask it.

We have a number of checksum the FCS (Frame Checksum) is normally done by t=
he NIC plus FCS errors normally do not transfer the frame into memory. The =
other Checksums UDP, IP, TCP are done in hardware and software depending on=
 the NIC being used. Need to read the docs for the NIC and then look at the=
 config or setup of the RX/TX for that NIC in the example applications.

>=20
> Thanking you,
> Param

Regards,
Keith