DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Balasubramanian, RajaramanX" <rajaramanx.balasubramanian@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Viswanathan, AnandaramanX" <anandaramanx.viswanathan@intel.com>,
	"Venkatachary, GunaseelanX" <gunaseelanx.venkatachary@intel.com>,
	"Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>,
	"S, Deepak" <deepak.s@intel.com>,
	 "Theerthala,
	Shanmukha SreedharX" <shanmukha.sreedharx.theerthala@intel.com>,
	 "Shemail, AhmedX" <ahmedx.shemail@intel.com>,
	"Godithi, Vasantha KumarX" <vasantha.kumarx.godithi@intel.com>
Subject: [dpdk-dev] hw checksum offload feature issue
Date: Thu, 15 Sep 2016 02:34:01 +0000	[thread overview]
Message-ID: <E92996B09255F049A3A3C3BD3C1C98DDD8970F@FMSMSX108.amr.corp.intel.com> (raw)

Hi,

    We are developing CGNAT VNF over DPDK. In that, we have NAT64 feature included which basically does IPv6 to IPv4 NAT translation and vice versa.

    When we do conversion from IPv6 to IPv4, we have used dpdk mbuf library function  rte_pktmbuf_adj() to remove 20 bytes of IPv6 header at the beginning and create IPv4 header and other headers appropriately.

  Also, we have hw checksum offload feature enabled. So when the packet goes through NIC hw checksum, apart from calculating IPv4 and UDP/TCP checksum, it also modifies other header fields like eth header dest address field.

   SO, have you come across any issue like this ??

  When we disable hw checksum feature, packet header fields are not modified and there is no issue.

Thanks,
Rajaram.

                 reply	other threads:[~2016-09-15  2:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E92996B09255F049A3A3C3BD3C1C98DDD8970F@FMSMSX108.amr.corp.intel.com \
    --to=rajaramanx.balasubramanian@intel.com \
    --cc=ahmedx.shemail@intel.com \
    --cc=anandaramanx.viswanathan@intel.com \
    --cc=deepak.s@intel.com \
    --cc=dev@dpdk.org \
    --cc=gunaseelanx.venkatachary@intel.com \
    --cc=kannan.babu.ramia@intel.com \
    --cc=shanmukha.sreedharx.theerthala@intel.com \
    --cc=vasantha.kumarx.godithi@intel.com \
    /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).