DPDK usage discussions
 help / color / mirror / Atom feed
From: Kumaraparameshwaran Rathnavel <krath@cloudsimple.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Network Drivers
Date: Thu, 22 Dec 2016 09:44:30 +0530	[thread overview]
Message-ID: <C1A6AD25-137B-47B3-A511-0507BCD0B7A1@cloudsimple.com> (raw)
In-Reply-To: <4F04B62A-306E-44A4-A1FC-0B7B9BF21585@intel.com>

Sure Keith. Will do that. Thanks for the response.

Thanking You,
Param.
> On 22-Dec-2016, at 3:44 AM, Wiles, Keith <keith.wiles@intel.com> wrote:
> 
> 
>> On Dec 21, 2016, at 10:46 AM, Kumaraparameshwaran Rathnavel <krath@cloudsimple.com> wrote:
>> 
>> Hi All,
>> 
>> When I use the network Drivers provided by the API is the CRC error checking 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 the 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.
> 
>> 
>> Thanking you,
>> Param
> 
> Regards,
> Keith
> 

  reply	other threads:[~2016-12-22  4:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 16:46 Kumaraparameshwaran Rathnavel
2016-12-21 22:14 ` Wiles, Keith
2016-12-22  4:14   ` Kumaraparameshwaran Rathnavel [this message]
2016-12-27 19:26 Kumaraparameshwaran Rathnavel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C1A6AD25-137B-47B3-A511-0507BCD0B7A1@cloudsimple.com \
    --to=krath@cloudsimple.com \
    --cc=keith.wiles@intel.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).