DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Tim Deng" <dpdkdev@126.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] ixgbe tcp cksum offload
Date: Mon, 25 May 2015 18:50:49 +0800 (CST)	[thread overview]
Message-ID: <6846b5e9.f47c.14d8ab24a93.Coremail.dpdkdev@126.com> (raw)
In-Reply-To: <20150525102848.GA8820@bricha3-MOBL3>

Thanks Bruce so much! That perfectly solves my problem.
Tim


At 2015-05-25 18:28:48, "Bruce Richardson" <bruce.richardson@intel.com> wrote:
>On Mon, May 25, 2015 at 06:15:23PM +0800, Tim Deng wrote:
>> Hi,
>> 
>> 
>> I am trying to use ixgbe tcp cksum h/w offload by following steps:
>> - populate pseudo cksum
>> - set l2_len, l3_len, l4_len
>> - set ol_flags
>> 
>> 
>> But I found the pkt doesn't get right h/w checksum by sniffing on recv side, and TCP cksum still leave with the original pseudo cksum. 
>> And I verified those meta are correctly set, e.g. a TCP syn pkt:
>> l2_len = 14, l3_len = 20, l4_len = 40 (with some tcp options),
>> and ol_flags = 0x90000000000000 which means PKT_TX_IPV4 | PKT_TX_TCP_CKSUM
>> 
>> 
>> Did I miss any step?
>> 
>> 
>> Thanks in advance,
>> Tim
>> 
>Check that you have not got TX offloads disabled in your port configuration. If
>you pass in NULL for the rte_eth_txconf pointer on tx queue setup, then offloads
>will be disabled. To get offloads such as checksums to work, you need to explicitly
>set the flags to allow them. (Generally, this means just setting txqflags to 0)
>
>Regards,
>/Bruce
>

      reply	other threads:[~2015-05-25 10:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25 10:15 Tim Deng
2015-05-25 10:28 ` Bruce Richardson
2015-05-25 10:50   ` Tim Deng [this message]

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=6846b5e9.f47c.14d8ab24a93.Coremail.dpdkdev@126.com \
    --to=dpdkdev@126.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@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).